Memory Leak in Protools 10...?

[shameusf]

Hi all,

Does anyone else experience regular memory leak type problems? The following is a regular experience for me. I open my macbook pro and protools 10 session in the morning. By the late afternoon to just hits the wall. The whole mac becomes super slow, I get the spinning beach ball of death and I get a 'Protools can't read fast enough from your disks' type message after only a few seconds of playback.

If I turn the machine off for a few hours, it's usually fine. No idea. It's happened for the last 18 months but more frequently recently.

I'm running a 2.4 GHz Core i& with 8 gb and two external G drives for audio and samples. All optimisations are in play...

Thanks,

Jim

[Darryl Ramm]

First thing to suspect is plugins. Are they all the latest? You may need to move aside plugins from their folders and see if this problem goes away. start by removing plugins you are not using. Then all the rest.

[shameusf]

Thanks for that. I'll give it a try.

I have had considerable problems with Kontakt 5, although everything seems up to date. Studio Drummer is practically unusable so I'm avoiding it. Could be other Native Instrument plug ins.

[Craig F]

You might want to host the VIs out side of Pro Tools in something like VE Pro
Or are you holding out for 11 and everything ported?

[Chief Technician]

Originally Posted by shameusf

I have had considerable problems with Kontakt 5,

I have found the stability of Native Instruments to be sketchy at best.

If you can, keep Activity Monitor (/Applications/Utilities) open while you are working. If there is a memory leak, you should see the amount of free memory slowly approach 0 MB.

[musicman691]

Originally Posted by Chief Technician

I have found the stability of Native Instruments to be sketchy at best.

If you can, keep Activity Monitor (/Applications/Utilities) open while you are working. If there is a memory leak, you should see the amount of free memory slowly approach 0 MB.

I must be odd man out then because I've had no stability problems with any NI stuff. I don't think it's a memory leak as such with Kontakt but rather that K5 doesn't automatically unload all samples when you quit it; some still stays in memory, no matter whether you're using Kontakt Memory Server or not. The again with 32 gig of ram I've a LONG way to go to running out of ram

[Cheesehead]

I'm afraid its a known issue.

There are lots of threads on it in the post production forum, where users with large film sessions are continually pushing the memory limits of PT10.

I have a current session that will only run for a couple of hours each time before crashing out. Unless I constantly watch the memory usage and keep re-starting PT.

Very annoying, but this is what PT11 fixes.

[musicman691]

Originally Posted by Cheesehead

I'm afraid its a known issue.

There are lots of threads on it in the post production forum, where users with large film sessions are continually pushing the memory limits of PT10.

I have a current session that will only run for a couple of hours each time before crashing out. Unless I constantly watch the memory usage and keep re-starting PT.

Very annoying, but this is what PT11 fixes.

Actually the way to clear things totally is to reboot the computer. Just restarting PT won't help clear the leak - it just adds up.

[Darryl Ramm]

Originally Posted by musicman691

Actually the way to clear things totally is to reboot the computer. Just restarting PT won't help clear the leak - it just adds up.

If it is a memory leak in Pro Tools or a plugin hosted in Pro Tools then exiting Pro Tools absolutely will remove any memory that has leaked. If not you have a serious problem in the operating system or maybe are confused and not looking at the proper memory stats.

[musicman691]

Originally Posted by Darryl Ramm

If it is a memory leak in Pro Tools or a plugin hosted in Pro Tools then exiting Pro Tools absolutely will remove any memory that has leaked. If not you have a serious problem in the operating system or maybe are confused and not looking at the proper memory stats.

I know when I ran Windoze systems the only way to cure a memory leak for good was to reboot the computer. And I know what I'm looking at.