id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc	blockedby	blocking	notify_on_close	platform	project
5348	Windows crashes faulthandler sometimes reports many fatal exceptions	Tom Goddard	Tom Goddard	"How is it that the Python faulthandler module is reporting many fatal signals on Windows in some crash reports?  It seems like one fatal signal should end the process.

An example is ticket #5332 where 3 identical python stack traces in show_open_file_dialog() are given followed by 3 identical python stack traces in show_save_file_dialog().  All 6 stack traces list the same thread id.

An example of normal faulthandler stack tracebacks on windows is ticket #4836.  Two tracebacks are shown, one for the ""Current thread"" and one for another thread with differing thread ids.

Possibly these multiple faulthandler tracebacks only occur when show_open_file_dialog() (14 crash reports) and show_save_file_dialog() are used and may be some oddity of QFileDialog.getOpenFileNames() or QFileDialog which is a base class for the save file dialog.  It would be interesting to know if we have had any reports where faulthandler produced multiple tracebacks that were not in either of these routines.  I don't remember any and am not sure how to search for those  (might look for multiple occurrences of ""Current thread"" in a ticket).
"	defect	closed	moderate		UI		not a bug		chimera-programmers				all	ChimeraX