I've reported this issue to Cakewalk support and they've been helpful but have still not been able to reproduce the issue I'm seeing locally.
I suspect that CAL might have a memory corruption bug that is triggered by the 'Split Notes to Tracks' script. Whenever I run the script on downloaded drum MIDI parts, I always end up with tracks that are really long (at least 2x the length of the original tracks). At some point subsequent to running that specific script, I inevitably encounter the WSOD. This usually occurs after doing things like changing the CAL generated tracks; bouncing to clips or slip editing them.
This is the only crash I've experienced regularly with Sonar, but I can pretty much set my watch by it whenever I need to do a 'Split Notes to Tracks' workflow. This happens even in Sonar only land (TTS1 for MIDI target).
I've gotten used to hitting Ctrl+S frequently so I'm pretty good at not losing stuff, but the crash is annoying.
 

I have rarely used CAL scripts but have seen that one mentioned a lot for drums. Is the original clip of a specific type (groove, manually recorded, etc.)?

The last official word on CAL that I recall is from 2009 http://forum.cakewalk.com/FindPost/1886369. For best results avoid instrument tracks in projects where scripts like "Split Notes to Tracks" are run. Development on CAL was stopped well before instrument tracks were added to SONAR.

It is kind of hard to imagine CAL being the culprit, but a memory glitch/corruption issue is very very likely somewhere in sonar.    Cal is a great feature, but it is very limited: change a thing, delete a thing, add a thing.   I'm sure the code is fairly large by now, but if someone were to grep for an array with numbers defining the size, someone might find a big oops.
 
 

I tried to run "split notes ..." recently ... a few months ago maybe.  I've never seen so much weirdness!  Scared me so bad I've not touched anything related to CAL since.
 

Hi - I am moving this to the Sonar forum for now, as it does not seem to have been confirmed as a bug.  
 
There will be a link in the Problem Reports showing the thread was moved, and it will point back to its new home in the Sonar forum.
 
Bob Bone
 

Split notes to tracks work fine, BUT, in order to avoid weirdness, move the track to be split so that it is the very last track. Then run the CAL script and start the split tracks at the next track number.
 
Regards,
Dan
 

dcumpian
Split notes to tracks work fine, BUT, in order to avoid weirdness, move the track to be split so that it is the very last track. Then run the CAL script and start the split tracks at the next track number.
 
Regards,
Dan
 

Thanks Dan.  I'll try to remember that for the next time.

Wow - good idea, Dan - hadn't thought of that.  I LOVE these forums.
 
Some of the CAL scripts are pretty long in the tooth, but the ones I have run have worked OK, though I usually read through them first, to try to look for any notes on their usage, or to try to figure out the code and what it wants, as well as verifying what it is trying to do.
 
@BobF - did that work for you?
 
Bob Bone

robert_e_bone
Wow - good idea, Dan - hadn't thought of that.  I LOVE these forums.
 
Some of the CAL scripts are pretty long in the tooth, but the ones I have run have worked OK, though I usually read through them first, to try to look for any notes on their usage, or to try to figure out the code and what it wants, as well as verifying what it is trying to do.
 
@BobF - did that work for you?
 
Bob Bone

Yeah, any CAL that has to create tracks isn't aware of all of the changes that have occurred since 1998. Moving the track(s) to the end gets all of the new stuff, like lanes and folders, out of the way.
 
Regards,
Dan