Cakewalk Stays In Memory After Exit / Cannot Re-Launch

[Adam Grossman]

Hello,

 

So I have had this problem for so many years dating back to at least Sonar X3.  But sometimes I close out of the program and it still stays in memory.  I can't reopen unless I kill it from here.

 

Any ideas?

 

[Bristol_Jonesey]

Is your interface still switched on?

If so it might well be preventing the Cakewalk app to close properly

[chris.r]

I just recently wrote in another thread about this same exactly problem that I have:

For me it's more a combination of these plugins is the problem rather than driver. How can I check it?

[Adam Grossman]

11 hours ago, Bristol_Jonesey said:

Is your interface still switched on?

If so it might well be preventing the Cakewalk app to close properly

yes it is, but this has happened with numerous different setups over the years with different interfaces.

[sjoens]

It will also (initially) fail to open after the splash screen if ANY other program is using ANY other sound device. This and the OP's issue have been a constant feature set shared by NO other DAW or program. ?

"Exclusive control" is deactivated.

This and the OP are my most requested fixes before any other feature or bug fix.

(Edited)

Edited May 9, 2021 by sjoens

[timboalogo]

I've had it happen if 1) samples haven't finished loading and I close the project or 2) a misbehaving plug-in and just right click on Cakewalk in Task Manager and close it manually.

[sjoens]

For me, in these 2 cases, the Task Manager trick never works. Usually requires shutting  it all down with a system reboot.

Sometimes the (initial) Fail to Open scenario can be fixed by closing the offending program which releases the audio. 

(Edited)

Edited May 9, 2021 by sjoens

[chris.r]

22 minutes ago, sjoens said:

For me, in these 2 cases, the Task Manager trick never works. Usually requires shutting  it all down with a system reboot.

Sometimes the Fail to Open scenario can be fixed by closing the offending program which releases the audio. 

That actually looks like interface driver conflict as opposed to what seems happening in my case or the topic starter.

In my case Cakewalk Application stays in Background Processes occupying around 685MB of memory. @ADUS do you use any particular plugins/soft synths when this is happening?

[sjoens]

Sorry, by Fail to Open I meant initially opening CbB when another program is using any type of audio source.

Edited May 9, 2021 by sjoens

[Noel Borthwick]

If it fails to open (or close) capture a dump file from task manager and send us a link. That will show why its hanging.
Instructions for capturing a crash dump manually are in the FAQ and my signature.

[sjoens]

Problem is, it doesn't open so it's not in memory or listed in Task Manager. 

Windows Report.wer file may have clues?

If so, I have 68 of 'em from 11/1/20 to 5/9/21.

Report.wer

Edited May 10, 2021 by sjoens

[Alan Tubbs]

Sometimes my cakewalk freezes etc. and after I close it down the midi activity icon in the bottom right corner of the task bar (the one with usb discount icon) is still live.  Open and shut down cakewalk fixes that problem.  Work around that works.

[craigr68]

I've been having frequent hangs on exit also for last month or so.  Don't run anything 32bit that I'm aware of.  Often Taskmgr won't close it.  Sometimes command line taskkill will stop it but it's stubborn, often taking a while or multiple repeats of taskkill.  Sometimes requires reboot.  I just submitted problem report and link to dump of recent hang according to the FAQ dump procedure using procdump64.

[Tom Richards]

Is there any fix for this issue?  I love my Cakewalk, but it's extremely annoying to have to restart my computer ever time I put it to sleep.  Please help!

[chris.r]

I've reported my issue along with the dump files already months ago but they (support staff) are always kindly asking me to update Cakewalk to the latest version, as if it makes any difference. The problem is, on my production machine I'm not updating Cakewalk every time new release is published, I just can't afford breaking compatibility with ongoing projects, so I'm constantly lagging a version or two behind the most recent release. So I'm stuck in a kind of loophole with it, bumming.

Edited July 16, 2021 by chris.r

[sjoens]

It seems Cakewak runs BEST on a system running only Cakewalk.

[Harddrive]

I sometimes get critical hangs on my Cakewalk which results in me binning the program, but it stays resident in Task Manager preventing a restart of the App.

This is only remedies with a reboot. 

It used to happen with Sonar 8 as well

HARDDRIVE

[Anders Madsen]

What harddrive said: Me too.

[Byron Dickens]

On 7/16/2021 at 10:36 AM, chris.r said:

I've reported my issue along with the dump files already months ago but they (support staff) are always kindly asking me to update Cakewalk to the latest version, as if it makes any difference. The problem is, on my production machine I'm not updating Cakewalk every time new release is published, I just can't afford breaking compatibility with ongoing projects, so I'm constantly lagging a version or two behind the most recent release. So I'm stuck in a kind of loophole with it, bumming.

How is updating going to break compatibility with ongoing projects?

[Clovis Ramsay]

While in Task Manager, locate Windows Explorer and select it as if you were going to end task, except it gives you a “restart” button that will correct most issues that pertain to hung programs or misbehaving drivers and a great way to regain control over a fussy GPU.  
 

Your icons and windows will disappear for a second and you will only see your desktop background but once Explorer re-executes, it all comes back.  Its a great option if you do not want to sign out of your account or restart the OS.