ProTools Critical Memory Error

[TimNielsen]

OK, maybe someone can shed light on this.

Working in PT 8.03cs2 tonight, making a bit of music, working with Play and Kontakt, has been working fine for days. Not a big session, one instance of each plugin.

Working, and all of a sudden, I get a 'ProTools is critically low on memory' error. WTF. So I check iStat menus, which tells me how much memory an app is using. And PT is using 1.24 gigs. I have 10 gigs of ram in my system, and at that moment 75% of it was free, unused.

Before I can even restart, PT just quits.

Um, hello, 1.24 is nowwhere NEAR the 4 gig limit for an app, so what the hell is going on?

[TimNielsen]

Oh lovely. Open my session back up, and 1) all my track colors have randomly CHANGED, 2) Kontakt is empty, none of my instruments that were saved with the session are there anymore, 3) it SOUNDS DIFFERENT!!!! Something is now gingked with my levels on the reverb sends.

RRRRRRrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr..

[ed13adema]

It happens with Auto Tune Evo with me

[kayakaya]

Same Problem......

[D'Animation]

I have been getting this recently on 8.01cs1 - usually its when i've been turning delay comp on/off to try get itself working again - sometimes got rid of it by bumping the H/W buffer up to the max, saving session, reopening it and dropping the buffer back to what your norm is
D

[BradLyons]

The only time I've seen this was when I was on my previous Windows machine---it appeared to me that it was referring to the PTHD cards, not the physical ram itself. Running Digitest would fail, it ended up being a bad card. I'm not saying that's what it is in your case---because I have heard a few others have this issue and their cards were fine. It's a very rare thing, but an annoyance.

[gonzolagonda]

This happened to me for the first time ever yesterday evening. I also had about eight instances of Autotune Evo (which is more than I've ever used before with this version of PT), so perhaps that is the cause as suggested above.

[elicious]

ya, evo sucks down bout 100mb ram per instance;
so, either audiosuite 'em
or use evo for the more detailed graphical instances
and switch to at5 (still in your folder)
for less critical "auto" ones.
5 uses far less ram.
tho, this does not seem to relate to tim's issue...

b.o.l.
e

[D'Animation]

Originally Posted by elicious

tho, this does not seem to relate to tim's issue...

No autotune here either...

[TimNielsen]

Yeah, I don't own autotune, but thanks for the idea.

This was a very simple session, the only two plugs running were Kontakt and Play. I have to chalk it up to an error with one of them, since they're both known to be pretty buggy. But still, I wasn't anywhere near 'maxing out memory' for PT, which is why this was so annoying.

I have four instruments loaded, two in Kontakt and two in Play, and since disk streaming was being used for all, the memory footprint should have been low.