Author lemburg
Recipients amaury.forgeotdarc, lemburg, pitrou
Date 2013-04-12.14:23:23
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <516818D1.6000409@egenix.com>
In-reply-to <1365775240.24.0.903789691624.issue17703@psf.upfronthosting.co.za>
Content
On 12.04.2013 16:00, Amaury Forgeot d'Arc wrote:
> 
> Amaury Forgeot d'Arc added the comment:
> 
>> At the time the Py_AtExit functions are called, the thread state is NULL
> 
> I'd say this is the root cause. It's a bad thing to call Py_DECREF without a thread state.
> Was it the case in previous versions?

The extension has been using this ever since it was written many
years ago and without any problems in all Python versions up, but not
including 2.7.4. It's the only way to do module cleanup in Python 2.x.

So far, we've only seen the problem for dictionaries that
are DECREFed.

I know that things may go wrong when DECREF'ing objects this late in
the finalization process, but still expect Python to handle errors
gracefully without segfaulting, as it has been the case for all
previous Python versions.
History
Date User Action Args
2013-04-12 14:23:24lemburgsetrecipients: + lemburg, amaury.forgeotdarc, pitrou
2013-04-12 14:23:23lemburglinkissue17703 messages
2013-04-12 14:23:23lemburgcreate