Participating Frequently

Question

Flash CS6, QuickTime: The export operation failed because it ran out of memory.

Forum|Forum|13 years ago
June 1, 2012
14 replies
95438 views

Exporting a QuickTime movie file seems to be an old issue with previous versions too. In CS6 I always get the error message: "The export operation failed because it ran out of memory." I've got tons of memory and have allocated increasing amounts to the cache with no success.

My small and fairly simple file was created with Flash CS5 which seemed to work fine at the time of creation. I've tried everything recommended online but with no luck so far. BTW, I reinstalled CS5 and tried that too but it just hangs now, and there's no error message.

Does anyone have a solution?

(OS X 10.7.4)

This topic has been closed for replies.

Show previous replies

R

Riccardo Sallusti

New Participant

I did a very deep test about this issue (out of memory while exporting to mov) and partially understood its behaviour:

In all this tests I've always used the "After time elapsed:" option.

- issue is not happening in CS5, both "in memory" and "on disk" setting works.

- issue is happening in CS6 if original fla document size is HD (1920x1080): even creating an empty movie of that size, and then trying to export the mov causes the issue!

if I reduce the size to 1280x720, for example, the export works and the mov is created correctly. In every case I had to set the "on disk" option.

The "on memory" does not work.

OSX 10.6.8

L

laptopleon

Participating Frequently

@Riccardo I only tried this in CS6. Others have claimed it works fine in CS5. That's interesting to know, but hardly a solution IMHO.

I don't think it's just the resolution, because very short HD animations did export fine here, if I recall correctly. If a certain amount of memory is exeeded, it runs out of memory. Even if you have much more hardwired memory available.

What seems to happen is this: Flash renders the movie frame by frame and just puts every pixel in the RAM memory. Because it doesn't compress anything at this level, the amount of raw pixel-data is huge. It doesn't matter what the size of a frame is, but of course with frames of 1920x1080, you will hit the problematic limit much sooner than with 1280x820. Then it's the x limit and stops the operation.

R

Riccardo Sallusti

New Participant

I totally agree with you: the problem is related to bad memory usage/management.

But I've tried again one minute ago to export to mov an empty movie of 60 empty frames sized 1920x1080 and it throwed that error again...

L

lauracostelloe

New Participant

I'm having the same problem in CS5.5.

I have an animation with no actionscript, a computer with plenty of free memory. I restarted Flash to clear any performance memory.

I don't have Adobe Premier so I can't use a different program, and Quicktime won't allow me to open a SWF file.

It's 30seconds long and I just want to export a .mov file!

I have tried changing all the settings.. I just don't understand why this function isn't working!

Did anyone find any other solutions to this?

L

laptopleon

Participating Frequently

Like I said.. open the .swf with Premiere Pro and it will render it, no matter how big it is.

M

Miller Studio

Known Participant

Under "QuickTime Export Settings" there is a radio button selection for "Store temp data:". Change it from "In memory (recommended for higher frame rates)" to "On disk (recommended for longer movies). Try that.

2

231212Author

Participating Frequently

Thanks, but that's one of the first things I tried. The only workaround has been using CS5 instead of CS6.

Marcus Kihn

Participating Frequently

Hi all

I was having the same issues. I've got a simple animation and started getting the Out of Memory error during the "Recording Flash Content" part of the export to Quicktime in CS6.

After trying a few things, it seems that what was causing the problem for me was a Bad Action script at the end of the timeline. (ie. there was a "goto next scene" and there was not another scene). I deleted that action and the export seems to work fine. I even added in a "stop movie" action at the end just to see if it was ALL actions that caused this and it also worked fine.

I called Adobe as well and they said this is a known issue and are working on it. So, Its seems that if you have strange actions, they cause errors.

2

231212Author

Participating Frequently

Well, I found sort of a solution here (http://www.kirupa.com/forum/showthread.php?275007-A-note-to-those-using-quot-Export-Movie-quot) but using CS5. My excuse is that it's Friday evening and my brain is tired. But CS6 still doesn't work.