Most of the time when I work on music projects, my work time is concluded with (and due to) a Sonar crash. I have come to accept this as the norm, though every session is concluded with a string of expletives at Cakewalk. Knowing how time-consuming it is to track such things down, I have just lived with it.
However, one thing seems really troubling, and that is that I can't get SONAR.EXE out of memory after it crashes, which requires a complete reboot of the PC. After a crash, the Task Manager shows Sonar right up top consuming 2Gb of RAM. Choosing End Process does not clear it out. Any idea what's happening?
Also, because my projects are thick and complex, they can take 5+ minutes just to load, so on the occasions where a Sonar crash does not end my working session I will leave the project open, and sometimes it is a few days before I can get back to it. I only use the computer for Sonar, iTunes and light web browsing. Is there a reason why leaving a project open like that would cause problems?