[issue9901] GIL destruction can fail

Changes by Antoine Pitrou : -- status: pending -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://

[issue9901] GIL destruction can fail

Antoine Pitrou added the comment: Committed in r84927. -- resolution: -> fixed stage: needs patch -> committed/rejected status: open -> pending ___ Python tracker ___ __

[issue9901] GIL destruction can fail

Antoine Pitrou added the comment: Moving the _PyEval_FiniThreads() call to Py_Initialize() solves the issue: diff -r 9e49082da463 Python/pythonrun.c --- a/Python/pythonrun.cMon Sep 20 12:46:56 2010 +0200 +++ b/Python/pythonrun.cMon Sep 20 13:41:47 2010 +0200 @@ -217,8 +217,15 @@

[issue9901] GIL destruction can fail

Antoine Pitrou added the comment: It is similar, but the issue is slightly different. Fixing issue1856 with the proposed resolution (the "stay_forever" flag) won't solve this, because the GIL mutex will still refuse to be destroyed if other threads reference it at the same time. --

[issue9901] GIL destruction can fail

Amaury Forgeot d'Arc added the comment: looks similar to issue1856 -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubsc

[issue9901] GIL destruction can fail

New submission from Antoine Pitrou : test_finalize_with_trace (in test_threading) sometimes fails because of failing to destroy the GIL (in _PyEval_FiniThreads()). This can be reproduced quite reliably by launching several copies in parallel: $ ./python -m test.regrtest -j10 -F test_threading