This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author culler
Recipients Marc.Culler, Nythepegasus, culler, enki1711, epaine, guydestefano, i3p9, lukasz.langa, miss-islington, mlierley, ned.deily, pablogsal, robotson, ronaldoussoren, serhiy.storchaka, terry.reedy, thesamesam, wordtech
Date 2021-11-02.21:01:54
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
A (hypothetical) explanation: I think that each NSWindow maintains a queue of attached sheets.  Failing to call the [parent endSheet] method left the file dialogue NSPanel in the queue, although it had been ordered offscreen and so was not visible. Opening the NSAlert added it to the top of the queue.  Closing the alert caused it to be removed from the queue. But, since the queue was not empty, the window manager was supposed to orderFront the next sheet in the queue. That sheet was the file dialog, which had not been destroyed since adding it to the queue had incremented its reference count, and failing to remove it had not decremented its reference count.  But the separate process that handles events for the file dialog had exited long ago.  So that made the newly re-opened file dialog NSPanel into a zombie.
Date User Action Args
2021-11-02 21:01:54cullersetrecipients: + culler, terry.reedy, ronaldoussoren, wordtech, ned.deily, lukasz.langa, serhiy.storchaka, Marc.Culler, pablogsal, miss-islington, epaine, Nythepegasus, mlierley, i3p9, thesamesam, enki1711, guydestefano, robotson
2021-11-02 21:01:54cullersetmessageid: <>
2021-11-02 21:01:54cullerlinkissue44828 messages
2021-11-02 21:01:54cullercreate