In my application (a browser), there are two types of crashes which can occur:
- Python exceptions, i.e. I can handle the crash just when it happens and display a crash dialog immediately.
- Segfaults of the underlying library - there the application will immediately close, with the user either seeing nothing, or their OS' crash dialog ("qutebrowser.exe has stopped working..."). Then I'll show the crash dialog on the next start.
The dialog currently looks like this:
I expect my user to be rather technical, but I realize it's a potentially stressful situation, and sometimes the user will just want to get back to the state they were, as fast as possible.
This lead to me getting many crash reports I couldn't get any useful information from - the user just clicked "report" and then "restore tabs", without reading what the crash log said and that they should provide more information.
In retroperspective I can't really blame them, with the wall of text I'm throwing at them ;)
Before I fix this I wanted to get some feedback about how I'd improve this.
A quick mockup of what it maybe should look like: