I am now sadly, one of 'those other people' who seems to be generating  lots of crashes with Sonar Platinum......something I had been blessed with not having to deal with in the past....and was somewhat puzzled by the reports of annoying crashes by others.
I assume the fault reporter is still the best channel to pass on the event circumstances .......given , (I imagine) that the I.T support team is somewhat reorganizing /morphing at the moment.
Question is : What sort of description OR style of info on 'Steps that led to the Crash' should one give in the text box (ie: I.T Technical Jargon OR Lay person 'what I was doing at the time'.....
+ is it necessary to send this each time or is the dump file usually enough?
Cheers
 
 

Frankly I wouldn't waste your time reporting bugs right now. You don't know what will become of them. It may be that they'll disappear into the ether. There is very unlikely to be anyone monitoring fault reporter submissions at this time, and we have no way of knowing what the new team's plan is for the existing bug report system. You're far better off waiting until the new version of Sonar comes out, seeing if the bug still persists, and reporting it to the new team through whatever new channels they set up for doing that. 

Yeah .......Sorta guessed as much............Brave New World For All Of Us Hey !!!
Cheers Sharke .......
.....FH From OZ .........where incidentally.........Shark/e/s Rule  :)
You gotta try our water LOL

I disagree with Sharke's advice. Hmm, that doesn't happen often.
 
Here's another take on it: that problem report database represents one of the assets that BandLab has purchased, and is far too important to just delete. When development resumes, it's going to be a valuable resource for Noel & Co., whose first priority will be addressing existing issues.
 
Granted, we can't expect any immediate action to be taken, especially if your problem isn't specifically a SONAR bug. Still, feeding information into that database is an investment in our future.