➜

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 fvisconte
Recipients Aaron.Staley, amaury.forgeotdarc, cupcicm, fvisconte, neologix, pitrou
Date 2012-08-07.08:12:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1344327136.3.0.250559135195.issue13992@psf.upfronthosting.co.za>
In-reply-to
Content 
Hi, 

Following Manu's information I complete with what you asked. 
I repeated the bug described by Manu, with the same software in exactly the same conditions.

The corrupted object is one of our SQLAlchemy mapped object. Chances are that the bug came from SQLAlchemy.

Find joined the "thread all apply bt" output. I will investigate today on this bug and will try to find a quicker way to reproduce it in order to use an hardware watchpoint on object refcount.
History
Date User Action Args
2012-08-07 08:12:16fviscontesetrecipients: + fvisconte, amaury.forgeotdarc, pitrou, neologix, Aaron.Staley, cupcicm
2012-08-07 08:12:16fviscontesetmessageid: <1344327136.3.0.250559135195.issue13992@psf.upfronthosting.co.za>
2012-08-07 08:12:15fviscontelinkissue13992 messages
2012-08-07 08:12:15fviscontecreate