Opened 5 months ago

Closed 5 months ago

#17642 closed enhancement (fixed)

Prevent reporting of useless bug reports

Reported by: Tom Goddard Owned by: pett, goddard
Priority: moderate Milestone: 1.10
Component: Core Version:
Keywords: Cc: chimerax-programmers
Blocked By: Blocking:
Notify when closed: Platform: all
Project: ChimeraX

Description

In the 1.10 daily builds we reenabled reporting of Windows crashes. We may want to turn that off for the 1.10 release since it almost never gives useful info and wastes Eric's time processing the report.

Similarly Linux crash reports are almost never useful and we might want to not show the crash report panel on all or most Linux crashes.

We may also want to not show the bug report panel for ChimeraX versions older than the newest version. ChimeraX does not know if it is the newest version without a web query. We could change the new version check to record the most recent version in preferences. Another option would be to just not accept bug reports if ChimeraX was installed more than a year ago.

Change History (3)

comment:1 by Tom Goddard, 5 months ago

Milestone: 1.10

Probably need to make these changes at least a few weeks before the official release to make sure nothing goes wrong.

comment:2 by Tom Goddard, 5 months ago

I disabled ChimeraX 1.10 crash reporting on Windows and Linux. It is still enabled in 1.11 daily builds.

We decided in our June 2, 2025 ChimeraX meeting to disable crash reporting on Windows an d Linux for the 1.10 release since those almost never provide useful info. We also decided to leave them enabled in the daily build, but the Linux crash reports will require an email address to submit. On Windows we will initially not require an email address so that we can get data on whether Eric's fix for the open dialog crashes (disabling garbage collection while open dialog shown) solves that problem.

comment:3 by Tom Goddard, 5 months ago

Resolution: fixed
Status: assignedclosed

Done.

I made Linux crashes require email in ChimeraX 1.11 daily build.

Note: See TracTickets for help on using tickets.