We’re aware of these USB-related issues, and we know that USB driver is quite not reliable.
As I said in another post, a new USB driver is under development (with the goal to not loose the COM port at Windows system level on target reset), and we’re expected a lot of improvements from it.
Unfortunately, it won’t be ready for 2.1 release, but we’ve a good hope to have something functional within the end of the year (somewhere in Q4).
Concerning the backtraces topic, 2.0 release shouldn’t automatically retrieve backtraces when the device resets, but it’s true that it was the case with 1.2
Are you running the 2.0 release, and do you still observe that behavior?