Flame keeps crashing – out of memory??

[shababo]

Hi everyone-

I’m new to flame and have been teaching myself so don’t have a tech person nearby to ask. Been using Flame 2009 for a few weeks, everything is going well, yesterday though my project started crashing whenever I tried to process – specifically i was resizing from HD to SD, but I don’t think this is related.

Flame crashes and in the shell it says “Panic – Out of Memory” – though I seem to have plenty of available frames in the framestore. Anyway, I’ve attached a picture of the message and output of the shell.

Thanks so much.

-Ben

[Martin Furness]

Hey Ben,

I have run across that several times before. If im not mistaken you can go into your config.init and adjust your memory that way. You will have find a happy medium to where your box functions properly in both Batch and Action and the other modules. If you set your memory to high or to low you will feel it on process.

[Amin Ysh]

Thanks so much for getting back to me!! Trying to get this project finished asap.

I’ve only gone into the config.init file once to uncomment a deck. Looks like I need to change the MaxLibrarySize allotment… does you (or anyone else) have suggestions for an apporpriate size? It seems like mine is set around 240.

Thanks for you help.

-Ben

[pixelmonk]

Hi Ben,
First you need to find out how much RAM your box has, then go into the config.init file and check your memory keyword. I expect it is commented out, if so, uncomment it and (if your box is maxed out with 16G of ram) enter a value of 10G. The MaxLibrarySize has nothing to do with the amount of memory that Flame uses.

Paul

[Amin Ysh]

Thanks, Paul-

I’m not in front of the box right now, but I looked through the init.cfg manual from autodesk… is it the MemoryApplication keyword I’m changing?

What percentage of the RAM in my machine should I set it to?

-Ben

[pixelmonk]

“is it the MemoryApplication keyword I’m changing?”
Yes, that’s the one.
As far as percentage is concerned, I’d check with support on that, I work only 2K 12bit and have been advised to use 10 out of my 16G.

Paul

[Amin Ysh]

Paul-

Thanks so so much.

-Ben

[Amin Ysh]

Wanted to update the thread. It turns out the issue was the MaxLibrarySize keyword. My libraries were filling up and when the flame tried to expand them it had a memory panic. Maybe I was running up against the allocated RAM for the box – which is set to default and seems to be setting itself to 3000 MB.

Anyway, I just boosted my MaxLibrarySize to 400 MB and everything seems to be working well. I also keep my eye on the percentage of my library that’s free more often now.

[cyril conforti]

how much material do you have in a Library. from your snapshot your max size is bumping up to 240 meg, thats huge dude.

[Amin Ysh]

to respond to the last question, my library size was huge, it was because clip history was on.

i no longer use clip history.

[Shannon Gans]

@alatteri 28039 wrote:

how much material do you have in a Library. from your snapshot your max size is bumping up to 240 meg, thats huge dude.

Hi,

clip libraries heading towards and above 200mb are becoming very common. batchFX and the resulting clip history do push these sizes up but as you cannot turn off clip history with batchFX you just have to live with the size of the clip libraries being that large and the system taking a long time to back them up.

One item I did find was if you go too far (500mb) then the software intermittently hangs when loading clips in from a library.

Regards

Chris
Freelance Engineer.

[Author]

Posts