You would think that this would be a basic function that would be tested for a regression as part of take lane testing. My apologies if this has been reported or fixed in X3D. If this works on X3d, I would appreciate it if someone can confirm the issue or not.
 
Open new project with no audio tracks
1. insert audio track1
2. expand take lane
3. clone the inserted audio track1
4. CTRL-Z to undo track1 clone
5. CTRL-Z again
 
This crashes SONAR 100% of the time.
 
I expect the track to be removed without crashing
 
SONAR Crashes 100% of the time when hitting the last CTRL-Z
 
To the bakers - 43 minutes on a toll call is way too long to wait for support. You need to expand your hours and manpower for us end users who would like to report crashes over the phone. I don't have the problem reporter on my favorites, but it looks like a bad sign that I may have to.

CWBRN-22982
 

Confirmed under X3D, I have sent the crashdump to Cakewalk under CWBRN-22984

I don't get a crash on the second Undo, I just get a failure to undo Insert Audio Track. But I do get an "Exception thrown in destructor' error in winfrm.cpp on closing the project, and that crashes SONAR.
 
Something is definitely wrong with the Undo stack in this scenario because history shows:
 
Clone Track
Add Take Lane
Add Take Lane
Insert Audio Track
 
It should show Clone Track before the second 'Add Take Lane'.
 
 

FYI I followed #1 completely, consequently there was no actual audio in the project in order to reproduce this bug.

I did not insert any audio in my recipe and it crashes 100%. I had audio in my original discovery project but got the recipe to it's shortest flavor.

replicated by the bakers and forwarded to DEV.

Noted. Thanks..

Hmm... I had X3(b or c... I forget) crash hard after frantically hitting the undo binding repeatedly instead of using the History menu. I figured it was just because I was being a spazz and the program choked on the rapid fire commands I was sending it. Perhaps it actually had something to do with this.
 
However I have not had it happen since, not even a blip or lag, and I've been writing scratch tracks so there has been  a lot of "undoing" via the hotkeys as I experiment as well as setting up and deleting empty tracks and undoing edits.
 
Really aside from a significant slow down on startup between the b and c patch that crash has been the ONLY odd behavior I've experienced. Like I'm almost shocked at how well it's working after the whole X2 weirdness I was running into almost every half dozen moves or so.

If you follow the steps to the letter it will crash, maybe press CTRL Z again at the end.
On the first day I installed X3 there were lots of crashes down to third party software which I managed to successfully troubleshoot and fix. For me this is the very first crash I've had since then.