msmcleod
Three processes named Cakewalk does not equate to three instances. It's just three separate processes.
Exiting Cakewalk in the normal way, closes down the child processes it created and any memory they were using.
Abnormally forcing a shutdown of one process that may be responsible for shutting down the others is not a memory leak.
Unless Cakewalk is eating up increasing amount memory sitting there idle, then it's not leaking memory.
First of all, it is three processes of Bandlab assistant...
Secondly, Cakewalk.exe does the typical "continuous load splash screen" nonsense about 75% of the time I load it...this is running it from Start menu, running it from folder, running it from shortcut, running it with elevated privilege...pretty much 3 out of four times I go to load SonarSplat/or Cakewalk by Bandlab I get the splash screen (smaller box that indicates it is loading) and it friggin HANGS there until I come back 30 minutes latter and kill it in task manager.
It consumes my display screen space and you cannot minimize it or even see any other program since it maintains screen priority...
Third I know its a memory leak because I have loaded it in debug mode into VS...besides the fact that whe I end "Cakewalk.exe" in taskmanager
IT DOES NOT END AND CONTINUES REGARDLESS OF RELOADING EXPLORER/ETC...
Fourth:When in this state of perpetual existence inside of task manager it IS USING 12% of available memory in spite of no splash screen, no program actually doing anything at all...just a "Cakewalk.exe" task with no corresponding splash/program running.
So yeah memory leak...
I've had this DAW for 5 years it has run fine and I am updated on ALL Microsoft drivers/etc...Win 7 64 bit.
I am not trying to be argumentative, but I am not a novice and have been using this software for years...since the company folded it has been crap, no real support, no real help...I get it, we're lucky they even released a version at all, but I have paid for versions that has gone south since the company went belly up.