➜

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 ebfe
Recipients ebfe
Date 2012-11-24.19:23:18
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1353785000.68.0.88975991365.issue16547@psf.upfronthosting.co.za>
In-reply-to
Content 
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?
History
Date User Action Args
2012-11-24 19:23:20ebfesetrecipients: + ebfe
2012-11-24 19:23:20ebfesetmessageid: <1353785000.68.0.88975991365.issue16547@psf.upfronthosting.co.za>
2012-11-24 19:23:20ebfelinkissue16547 messages
2012-11-24 19:23:19ebfecreate