[issue16547] IDLE segfaults in tkinter after fresh file's text has been rendered

Lukas Lueg added the comment: self.io is set to null before the colorization is finished. When IDLE's text-window is closed, the AttributeErrors printed to stderr cause IDLE to crash due to #13582. One can also trigger the exceptions on any other OS as described in OP. While #13582 is an issu

[issue16547] IDLE segfaults in tkinter after fresh file's text has been rendered

Changes by Serhiy Storchaka : -- nosy: -serhiy.storchaka ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http:

[issue16547] IDLE segfaults in tkinter after fresh file's text has been rendered

Roger Serwy added the comment: Lukas, thank you for your persistence in trying to resolve this issue. The Windows traceback is interesting. I am wondering if a "race" condition may be causing this bug. Callbacks from the Tcl interpreter eventloop back into Python may be ordered improperly. A

[issue16547] IDLE segfaults in tkinter after fresh file's text has been rendered

Lukas Lueg added the comment: On windows, IDLE only crashes if executed via pythonw.exe; if executed under python.exe, the attached traceback is dumped to stderr -- Added file: http://bugs.python.org/file28136/excp_traceback.txt ___ Python tracker <

[issue16547] IDLE segfaults in tkinter after fresh file's text has been rendered

Lukas Lueg added the comment: Switching to ActiveState's TCL fixes the problem on MacOS 10.6 I won't be able to produce a trace for a debug-build on Windows; attaching a semi-useless trace anyway. -- Added file: http://bugs.python.org/file28135/backtrace_windows.txt __

[issue16547] IDLE segfaults in tkinter after fresh file's text has been rendered

Ned Deily added the comment: >From the backtrace it shows you are linking with the Apple-supplied Tk >(/System/Library/Frameworks/Tk.framework/Versions/8.5/Tk) framework. The >Apple-supplied Tk 8.5 in OS X 10.6 was the first release of the Cocoa Aqua Tk. >It has proven to be unusable with Pyth

[issue16547] IDLE segfaults in tkinter after fresh file's text has been rendered

Roger Serwy added the comment: On Mac, which version of Tk are you using? IDLE is known to have problems on Mac with Tk. See http://www.python.org/download/mac/tcltk/ You can disable colorization with the undocumented Ctrl+/ key combination. Does the crash still occur with the colorizer disabl

[issue16547] IDLE segfaults in tkinter after fresh file's text has been rendered

Lukas Lueg added the comment: using NSZombieEnabled and MallocStackLoggingNoCompact we can see the use-after-free behaviour -- Added file: http://bugs.python.org/file28099/malloc_history.txt ___ Python tracker ___

[issue16547] IDLE segfaults in tkinter after fresh file's text has been rendered

New submission from Lukas Lueg: IDLE crashes due to what seems to be a use-after-free bug. Opening a file from the 'Open...'-menu leads to a segfault after the text has been rendered. It seems this can be reproduced 100% of the time if the file is big (e.g. 150kb) and the window receives event