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 roger.serwy
Recipients ebfe, ned.deily, roger.serwy, terry.reedy
Date 2012-11-28.05:16:41
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1354079802.83.0.224486674467.issue16547@psf.upfronthosting.co.za>
In-reply-to
Content
I was able to trigger this problem on 2.7 as well. Changing type to behavior as the core interpreter is not crashing.

Lukas, the only way I can trigger the traceback is by closing the editor while the colorizer is still colorizing. Clicking randomly on the editor itself did not trigger the bug. Can you clarify what you meant when you said "window receives events (clicks...)"?


Closing the window place a <<close-window>> event on the Tk event queue.
Calling .update() causes Tk to process all events in the queue, including callbacks into IDLE. As a result, closing a window can trigger a few different use-after-free conditions.

I managed to trigger two of these in the __init__ of PyShellEditorWindow in Lib/idlelib/PyShell.py. The self.io reference can be set to None during EditorWindow.__init__(self, *args) or during self.restore_file_breaks().

The Lib/idlelib/ColorDelegator.py also has a .update() in its recolorize_main loop.
History
Date User Action Args
2012-11-28 05:16:42roger.serwysetrecipients: + roger.serwy, terry.reedy, ned.deily, ebfe
2012-11-28 05:16:42roger.serwysetmessageid: <1354079802.83.0.224486674467.issue16547@psf.upfronthosting.co.za>
2012-11-28 05:16:42roger.serwylinkissue16547 messages
2012-11-28 05:16:41roger.serwycreate