As many of us know, sometimes when Sonar/Cake crashes (often caused by plugins and audio drivers) the process still running in task manager cannot be killed. The best solution I have found for that is to switch off my audio interface and after a few seconds, the process will end. Most people don't know about that and are forced to reboot their system! This hung process issue can also occur when exiting Sonar/Cake sometimes which means when you try to launch Cake again, nothing happens.
This unstoppable process bug has been around for a long time and I frequently see posts here and on Facebook about it. Now, a friend who I recommended Cake and Bandlab to has sent me a very frustrated message regarding this very issue. It crashed, and he couldn't kill the process - many of us know his frustration. His reaction to it is fairly standard, "It's a buggy pile of cr*p!". The chances are Cake didn't crash because of a bug in its code, but most likely because of a plugin or driver. My concern is this: if you spend good money on software and it does this, you spend time and effort trying to resolve it, finding a fix, a workaround or reporting it, or living with it. If however, you got the software for free, you are more likely to give up, right it off as buggy freeware and uninstall it and then tell everyone it's no good.
This is probably
THE worst user experience someone can have with Cake and it is not uncommon - anyone who uses Cake for any time will experience this. All DAWs crash occasionally, but usually they will close cleanly leaving no processes running and can simply be relaunched. I really think it's about time Cakewalk/Bandlab fixed this unstoppable process issue. It would surely only require a few lines of error handling code! I can see this bug more than any other putting people off using it and going off and telling everyone else that, "It's a buggy pile of cr*p" and I don't think Bandlab or any of us want that!