X3c CRASHES on 'UNDO' keystroke CTRL-Z CWBRN-22982 - Still broke X3E

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.

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

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

replicated by the bakers and forwarded to DEV.

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.

I managed to reproduce the steps of the first post again with X3E.

According to release notes CWBRN-22982 is fixed in X3E but it isn't (could bakers please remove off release notes).
The crash dump has been sent as CWBRN-24856.

More info that may be helpful. On my system the steps do not result in a crash.  However, the second undo does not remove the inserted track, and closing Sonar results in sonarpdr.exe still being active in the Task Manager processes tab.  After ending this process, opening Sonar again results in a loud continuous noise in my system.  It goes away if I close Sonar, then stars again when I reopen.  It won't go away until I restart my sound card.  I have never seen the behavior before trying the specific steps outlined above.
 
Clearly something fundamentally screwed up here.  

I got an e-mail from the cakewalk trouble reporter that this was fixed and it is not. I followed the steps 100% and SONAR cratered with a report submitted to the bakers. SONAR did not crash right away, but trying to do anything else in SONAR crashed to desktop.