Memory leak fixed yet? Ever?

[RobbaDobba]

In searching back through the archives and seeing that many people posted "memory leakage" problems with 5.0 and 5.0.1, I'm wondering if any fixes, user or Digi founded, are found or on the horizon.

I allocate 64 megs to each PT 5.0.1 and DAE. Before opening PT, my OS 9.0.4 uses 40-45 megs. After quitting PT, it's using 58-63! Now, I have 320 megs of RAM, but it's still a pain in the you know what.

[RobbaDobba]

Hellooooo out there!!!

[evandaum]

I believe PT uses system memory for disk or DAE buffering, so naturally, it would get bigger when PT is running. I don't argue there may be leak issues somewhere, but I think the enlarged system size is the result of intended programming, not a mistake.

-Evan

[PacMan]

I don't know about the PT leak problem you're talking about, but it's not uncommon for the OS to use massive amounts of memory, even when not running PT.

Every new OS that comes out, keeps getting Bigger & Bigger !

I believe you need 128 just to run the Demo of OSX .

[Giulio]

Hi guys.
I think you missed the point...
What RobbaDobba means is that AFTER QUITTING Pro Tools, the system is using 10-20 Mb more than it did before. No more buffering, no more complex calculations...it just "ate" that RAM to do Lord knows what (Lord and Mr Digi, hopefully).
And, yes, it's annoying, esp when you are a bit short of RAM on your machine.
You know what...every time there's an annoying or embarrassing question Digi guys pretend that they haven't read it...

[RobbaDobba]

THANK YOU, GIULIO!!! Someone understood!

You're right, I don't recall seeing ANY DigiTechSupt replies on ANY of the previous postings about this problem.

This is an embarrassing glitch. Even my MICROSOFT software doesn't thieve as much RAM as this.

If anyone out there knows of any good utilities that might get this RAM back, let me know.

Or, if DigiTechSupt should cop to this glitch once and for all and alert us to a potential fix, I'm sure we'd all love to see it.

[HeLikesItHeyMikey]

Robba and others:

At last someone has let the genie out of the bottle!!! This NOT a Digi issue but an Apple issue, and you clear this problem by using a nifty tool called "OS Purge".

Listen up: Even turning the Mac OFF and rebooting will not buy back that lost ram allocation.

So here's what you do: run OS-Purge and it will automatically open "About This Computer" window to display used system ram. If it is STILL too high - reboot and ZAP the PRAM THREE TIMES!! (do this by holding down the option-command-p-r keys all at once while booting). This will not remove any data or damage anything in ANY way so get used to doing it because after EVERY hard system crash this memory issue will creep back up.

It is effectionately known as "memory fragmentation" and even my sampler has this issue and has a utility to "defragment memory".

Once I learned this (and believe me I thought I had NOOOOOOOOO problem) I was tickled to see I "bought" back like 30 megs worth of ram in one step

http://duc.digidesign.com/ubb/images/icons/grin.gif

[MacDaddy WGAR]

robba, in addition to os purge there is another utility you can find at Maxfixit in the library called Fix heap. it sometimes works where os purge will not.

BC

[RobbaDobba]

Thank you for all responding. If anyone else has anything to share, keep 'em coming!

[Giulio]

Does anybody have a link for this? I found the informations, but not the download.
Also, they say it's for Mac OS 7.6...is it ok for later systems?