Protools Memory Leak???!!!

[Agentemo1]

I am on of the few users who have had major problems with H/W buffer errors after 15 minutes of editing or doing anything..... i have found that when i watch task manager i have on gig of ram and protools starts off with 200,000K after 15 minutes it slowly rises to 940,000K then thats what crap hits the fan......somone please help or is it only a software fix..

Derek

Ok after much trouble shooting i have i think somewhat isolated the memory leak... I went back to pro tools version 5.3.3 on a bare system and no exrta plug ins.... memeroy was constant and up and down on usage... moved to versoin 6.1... same thing so were good up till i move to 6.7 where even with digi plug ins removed im still wathcing my memory sky rocket through the roof... ive talked to a couple other people who are programers and they say that its DEF not a hardware thing... and the only software i have is digi... it cant be windows i dont think cause 6.1 worked fine.... Digi please look into this... how do i get them to try and find out if this is them?

[Rail Jon Rogut]

Which plug-ins do you have installed.. remove all plug-ins (except the basics) and see if your problems persist.

Rail

[Dogcode]

Are you running dverb without a dither......just a guess....

[xraydelta1]

did you play with the h/w buffer settings?

[Agentemo1]

look at the top i updated my findings

[mrufino1]

What do you mean, D-Verb without dither? Are you supposed to run a dither plug after D-Verb? Does it cause cpu to hit the roof or memory to run out if you don't? I hadn't heard htis but it might explain some things if true...

[Ducky]

What do you mean, D-Verb without dither? Are you supposed to run a dither plug after D-Verb? Does it cause cpu to hit the roof or memory to run out if you don't? I hadn't heard htis but it might explain some things if true...

This is a long known issue. To spare the repeat, simply put a 16bit dither BEFORE D-Verb in 24bit sessions and the CPU won;t run away with itself. Search the DUC if you need more info.

[Agentemo1]

This is not a cpu problem im finding it in the memory