I know there’s been some interest in a Windows build with a built-in crash reporting tool. I’m always a little wary because some users understandably don’t want to report molecules (or cannot due to legal reasons).
I’m starting an optional build with the crashpad and sentry software added for Windows users. (Generally Linux and Mac users can already give stack traces.)
I’m looking for beta testers particularly if you’ve been experiencing crashes on Windows.
Can anyone help?
Some wording for feedback:
This is a diagnostic build of Avogadro. It can send a report to the developers when Avogadro crashes, which helps us fix crashes we cannot reproduce ourselves.
A crash report contains a snapshot of Avogadro’s memory at the moment it failed, along with your operating system, graphics driver and Avogadro version, and a log of recent activity. That memory snapshot makes the report useful, but it may incidentally include fragments of what you were working on, such as part of a file name or a molecule you had open.
And by the way, there’s a way to test the crash reporting itself. Run the build with --crash-test and it should intentionally trigger a report.
I like the message! The detail is good and is more than is usually provided in these kinds of pop-ups.
I think the dialog overall needs a more striking start or heading so that it’s immediately obvious what’s being asked for. “Help us improve Avogadro!” or “Do you want to help us improve Avogadro?” as either the window title or a standalone first line in bold, is what I’m thinking.
If it’s opt-in anyway, why not just put this in the normal builds? There’s plenty of open-source software that does this.
With regards to compliance with EU law, the most important thing is that there is absolutely no personally identifying information sent to or stored by the server. My impression has always been that as long as it’s all anonymous you can pretty much do what you want.
