Memory Leak [Sonitus FX delay]

skeewiff


Hi all. Have written about this bug elsewhere, but decided it needed its own post so as to not get lost.
 
Essentially, I have a memory leak in Sonar 8.5.3 32bit running on W7x64. It was manifesting itself as a lock up followed by crash and sponataneous reboot. So if anyone else is seeing a sequence of errors like this... read on!
 
I spent the last few days monitoring everything whilst I worked - temps, Cpu use and memory, and I noticed that just before Sonar locked up, The process sonarpdr.exe was using around 3.7 gig of memory (I would imagine the absolute limit for a 32 bit program).  At this stage Sonar's main arrange window becomes totally unresponsive, (although the mixer and synth racks still function) I am unable to exit Sonar and any attempt to kill the process results in a crash followed by spontaneous reboot. Loading the project from fresh showed a use of under 400mb, so something is definitely rotten in Denmark!
 
In my case, I had previously thought it was an incompatibilty with plug ins like Truepiano and Guitar rig, because when I opened them they would push Sonar "over the edge" and force the crash as detailed above. In hindsight I realise that they were just the straws that were inevitably breaking the camels back. Loading these plugs at a point when Sonars leak has not taken grip yet proves them to be working just fine. Red herring!
  
In the last few weeks I have purposefully limited myself to Cakewalk only plugs just to make sure that it wasnt an incompatibility with some 3rd party vsts. The last project I was working on contained only the following plugs and did eventually trip up. In fact I have it open now and I'm watching Sonar slowly munching up the ram. 
 
12x RXP player
2x Dropzone
8x Channel tools
4x Boost 11
5x Sonitus EQ (built in)
4x Sonitus Delay
2x Sonitus reverbs (1 on bus)
1x Sonitus compressor (with sidechain inputs)
 
So I guess the next question is - has anyone seen any memory leak issues with any of the above running 32bit in a 64bit OS? Or is the whole bit thing irrelevant as others are experiencing it in XP Pro.
 
Potentially, if the plugs were a suspect and we were assessing them on their behaviour, then sonitus reverb and delay are worth mentioning as neither work properly. Sonitus reverb seems to have problems with large decay times. It will intermittently create a large burst of speaker frying white noise at 0db which slowly fades away (the length of the reverb decay). Sonitus delay still has the same bug it had at release, which is that yet again, intermittently, using the low cut eq on it causes a 0db spike and causes the entire channel to go dead. Just thought I would mention this, as if this sort of behaviour goes unnoticed and unfixed - what else could be broken?
 
I have submitted this to cake ts as well so hopefully be able to narrow it down. I will also try to substitute the plugs starting with the sonitus to see if it is indeed plug-related.
 
Any other advice welcome.
 
Cheers!
 

JonD


Hi, I posted in your other thread.  In addition to the recently updated Presonus drivers, make sure you have the latest firmware for your FP10, as I believe they released a new version of that as well. 

It really is important these are fully up to date before you begin your troubleshooting.   (If you haven't communicated with Presonus recently, this may have been overlooked since the updates only came out this week).

Good luck.

bitflipper


12 instances of RXP sounds like a potentially big RAM-muncher, depending on the size of the REX files. What happens if you freeze those tracks and then re-open the project? Does the ever-increasing memory usage continue?

wintaper


While it is often a sign, constantly increasing RAM usage isn't necessarily a "leak". In this case you've got a lot of soft-synths running, they could be using a lot of RAM. It's likely the synths don't allocate all the RAM at load - but as you run them, the footprint increases. All of this is pretty normal.

I'd freeze all but one RXP, run the project as long as possible, and see if the RAM increase tops out. Repeat for each of the 12 (if you have the time)

The total size of all the rx2s loaded is 14.7 meg. I know this as I submitted them to cakewalk so they could load the project. I doubt this will push my machine over the top!

Is there any way of wrapping a plug so it disguises itself with the clsid of another?

Can anyone else give this a go and see if we can narrow it down to which OS's are affected.   I can confirm that it is happening in both 32bit and 64bit versions of Sonar 8.5.3 on Win7x64

brundlefly

Can anyone else give this a go and see if we can narrow it down to which OS's are affected.   I can confirm that it is happening in both 32bit and 64bit versions of Sonar 8.5.3 on Win7x64

I can not reproduce with SONAR PE 8.5.3 x64 on Win7 Home Premium. SONARPDR process memory remains between 85 and 87MB with one Sonitus delay on each of two tracks, and stays between 94 and 96 MB with two instances on each track.

brundlefly


Edit: I only have 4GB RAM.