Pro Tools Is Critically Low On Memory

[TinyE1017]

I've been getting this "Critically Low on Memory" a lot since I upgraded to 8. I purchased a new hard drive and installed Leopard. Then I installed PT8. I'm running a Mac Pro with a 2 x 2.66 Ghz Dual-Core Intel. With softsynths, it happens for frequently, but I removed all of my synths and RTAS plugs and it's still happening. Keeping an eye on the activity monitor shows that even when I'm not working the amount of RAM being allocated continues to creep up. I started with 9 gig of RAM and have moved down to 4 trying to discover if it is a hardware related problem and it hasn't changed.

It's almost as if there is some kind of memory leak. Overall, I love the new update, but it's a little sluggish and needs some fine tuning.

Any thoughts or help (or commiseration) would be appreciated.

Thanks!

[P A M]

got exactly the same problems, - usually in the context when using VI´s like Structure, Play ect... - but allso when using large instruments in Reason via Rewire..

[crizdee]

Hi,

I get this only when i first open a 7.4 session in PT8! once i re save as PT8 its fine.

Chris

[TinyE1017]

Tried doing a "save copy as" in a fresh new PT8 session with copied audio and such - still the same problem. Thanks for the idea, though. Any more....?

[C.Bayley]

I get this after ive been opening and closing a lot of sessions.It is some kind of memory leak ,or VI's not letting go of memory after session closes.This is an issue i had on my earlier G5 2.5 dual,im still getting it on my new MacPro
im composing for Tv and have multiple sessions that i open and close in my normal workflow.And i get the "critical memory" message ,or sometimes Pro Tools8 just disappears.Frustrating when you have anyhwere up to 20 different sessions for the one project that you need to keep working on.

[DigiTechSupt]

Can everyone experiencing this please post a list of installed plug-in versions using the Tech Support Utility from the General Troubleshooting thread?

I have a suspicion it's an old or unsupported plug-in that's the cause, but want to see for sure.

I've got a couple systems that I'm working with that contain VI's and Reason and I'm not seeing this problem, so I'd like to see what you're working with and compare notes...

[Oroz]

Originally Posted by DigiTechSupt

Can everyone experiencing this please post a list of installed plug-in versions using the Tech Support Utility from the General Troubleshooting thread?

Where's this Utility exactly? I can't find it. I'm getting that warning too.

[P A M]

Originally Posted by DigiTechSupt

Can everyone experiencing this please post a list of installed plug-in versions using the Tech Support Utility from the General Troubleshooting thread?

I have a suspicion it's an old or unsupported plug-in that's the cause, but want to see for sure.

I've got a couple systems that I'm working with that contain VI's and Reason and I'm not seeing this problem, so I'd like to see what you're working with and compare notes...

Aaaahhh, - you mean this:
http://duc.digidesign.com/showthread.php?t=30813


I can tell you right off the bat that there are NO unsupported plugs on my system - seriouslly no bs..
I have no idea how you test, but trust me, its happening when you use larger supported-up-to-date-latest-version-protools8-sertified-state-of-the-art-sampled instruments in medium-to-larger-sessions...

Cheers

[DigiTechSupt]

Originally Posted by P A M

Aaaahhh, - you mean this:
http://duc.digidesign.com/showthread.php?t=30813


I can tell you right off the bat that there are NO unsupported plugs on my system - seriouslly no bs..
I have no idea how you test, but trust me, its happening when you use larger supported-up-to-date-latest-version-protools8-sertified-state-of-the-art-sampled instruments in medium-to-larger-sessions...

Cheers

Ok, but which ones exactly? When you load the instruments are you watching your RAM usage and, if so, what's happening with it? Do you notice that doing any particular things makes the RAM usage go up? I'm running several VI's and samplers here and haven't noticed issues until I actually get to the point of using all available RAM...but that would be normal.

[P A M]

Originally Posted by DigiTechSupt

Ok, but which ones exactly? When you load the instruments are you watching your RAM usage and, if so, what's happening with it? Do you notice that doing any particular things makes the RAM usage go up? I'm running several VI's and samplers here and haven't noticed issues until I actually get to the point of using all available RAM...but that would be normal.

(I got 8 gigs of ram) intel quad, 4 discs ect... Anyway.
- an almost sure way of doing this is to have Structure in the session with some instruments loaded and use Reason via rewire. Load one of the Abbey Road pianos (granted they are large) and the try change an instrument in Structure...

Using Ivory and Structure is also a sure way of eventually getting the error.

If you have any good idea if something can be done I would be greatfull..

In 7.4.2 you could run into it with Velvet, - dont seem to be a prob in 8 tho..