But only when there's an un-named marker in 64 bit X3e.
 
32 bit X3e does not crash.
 
Try it and confirm... or not, so I can submit a bug report.
 
Thanks.

I can't reproduce this one, either.

I just tried it again and it crashes X3e 64 bit anytime I open Markers View. Whether there's any markers or not, named or not. I must have the most unstable 64 bit X3 installation known to man. It is so buggy I'm going to have to reinstall it or remove it.
 
Again, X3 32 bit does NOT crash.

It seems odd this wouldn't stay in the Problem Reports forum.

If you can get somebody else to reproduce it here we will throw it back, we need reproducible bugs in the problem reports forum...
This needs to be troubleshooted first, Sonar forums has more eyeballs.
 
I would recommend seeing if it crashes on a brand new project without a template.
 
Cheers...

I created a new project using the Normal template.
X3e x64 build 352: no crash!

what's in your project soens?

Today I created a brand new "blank" project. Opened Markers View in Multidock with no markers. Fine so far. In TV I insert marker "1". Fine so far. Click on Markers View in Multidock and I get the WSoD and "Sonar has stopped working" dialog.
 
Then I created a brand new "normal" project. Inserted a MIDI track. Opened Markers View in it's own floating window. No crash yet. In TV I inserted marker "1" and got the WSoD and "Sonar has stopped working" dialog.
 
Then I opened a project already containing markers. Opened Markers View and got the WSoD and "Sonar has stopped working" dialog.
 
As long as Markers View is open and a marker exists, Sonar will crash. This only happens in 64 bit X3, not 32 bit so to determine if the install is faulty I will do a new install later this week.
 
The crash does not invoke the 'send info to Cakewalk' dialog. Is there a way to make it do that?

I have no issues when I do it.

This might be a silly question, but how long do you give Sonar before forcibly closing it?
 
Sometimes with other aspects of the software, I have seen a "Sonar is not Responding" message, but more often than not, Sonar can resolve whatever conflict is causing the message and it runs happily again if I leave it alone for a few minutes.