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 adamtj
Recipients adamtj, asvetlov, ncoghlan, neologix, pitrou, rosslagerwall, vstinner
Date 2012-04-02.19:51:19
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
For what it's worth, I think I've seen this bug in 2.6 and 2.5, using generators created in python threads, while profiling not tracing.

I'm creating generators in one python thread and storing them in a variable.  In a different python thread I overwrite the variable, which garbage collects the generator.  Sometimes it causes an interpreter crash.  Other times, it seems to trigger a return event in the profiler, but it's associated with an incorrect thread.  The thread in question is often (always?) in the profiler code, so it looks like the profiler is profiling itself.
Date User Action Args
2012-04-02 19:51:19adamtjsetrecipients: + adamtj, ncoghlan, pitrou, vstinner, asvetlov, neologix, rosslagerwall
2012-04-02 19:51:19adamtjsetmessageid: <>
2012-04-02 19:51:19adamtjlinkissue14432 messages
2012-04-02 19:51:19adamtjcreate