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

[Lukas Lueg]

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 events (clicks...) while the colorization is going on.

I've been able to reproduce this behaviour on MacOS 10.6 (3.2, 3.3 and 3.4a) and Windows 7 (3.3) but not on Fedora 17.

Python 3.4.0a0 (default:a728056347ec, Nov 23 2012, 19:52:20) 
[GCC 4.2.1 (Apple Inc. build 5664)] on darwin




I'll attach a backtrace and a malloc_history (from a different trace). Any guidance on further debugging on this?

----------
components: IDLE
files: backtrace.txt
messages: 176307
nosy: ebfe
priority: normal
severity: normal
status: open
title: IDLE segfaults in tkinter after fresh file's text has been rendered
type: crash
versions: Python 3.2, Python 3.3, Python 3.4
Added file: http://bugs.python.org/file28098/backtrace.txt

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue16547>
_______________________________________