[issue6531] atexit_callfuncs() crashing within Py_Finalize() when using multiple interpreters.

Change by STINNER Victor : -- resolution: -> fixed ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue6531] atexit_callfuncs() crashing within Py_Finalize() when using multiple interpreters.

Change by Petr Viktorin : -- stage: patch review -> resolved status: pending -> closed ___ Python tracker ___ ___ Python-bugs-list

[issue6531] atexit_callfuncs() crashing within Py_Finalize() when using multiple interpreters.

Change by Eric Snow : -- status: open -> pending ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue6531] atexit_callfuncs() crashing within Py_Finalize() when using multiple interpreters.

Marcel Plch added the comment: > At a guess, the problem is because in atexit_callfuncs(): > >module = PyState_FindModule(); >if (module == NULL) >return; In #31901, I solved this problem by getiing rid of PyState_FindModule in the atexit code, using

[issue6531] atexit_callfuncs() crashing within Py_Finalize() when using multiple interpreters.

Change by Petr Viktorin : -- nosy: +Dormouse759, encukou ___ Python tracker ___ ___

[issue6531] atexit_callfuncs() crashing within Py_Finalize() when using multiple interpreters.

Nick Coghlan added the comment: See also https://bugs.python.org/issue31901, which reached a similar conclusion to this discussion (i.e. atexit functions should be run when the subinterpreter goes away). -- nosy: +ncoghlan ___

[issue6531] atexit_callfuncs() crashing within Py_Finalize() when using multiple interpreters.

Changes by Eric Snow ericsnowcurren...@gmail.com: -- versions: +Python 3.5, Python 3.6 -Python 3.2, Python 3.3 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6531 ___

[issue6531] atexit_callfuncs() crashing within Py_Finalize() when using multiple interpreters.

Graham Dumpleton graham.dumple...@gmail.com added the comment: What are the intentions with respect to atexit and sub interpreters? The original report was only about ensuring that the main interpreter doesn't crash if an atexit function was registered in a sub interpreter. So, was not

[issue6531] atexit_callfuncs() crashing within Py_Finalize() when using multiple interpreters.

Antoine Pitrou pit...@free.fr added the comment: That said, for mod_wsgi I have extended sub interpreter destruction so that atexit callbacks registered in sub interpreters are called. For mod_wsgi though, sub interpreters are only destroyed on process shutdown. For the general case, a sub

[issue6531] atexit_callfuncs() crashing within Py_Finalize() when using multiple interpreters.

Antoine Pitrou pit...@free.fr added the comment: Hmm something else: currently the atexit funcs are only called when the main interpreter exits, but that doesn't really make sense: if I register a function from a sub-interpreter, why would it execute correctly from another interpreter? All

[issue6531] atexit_callfuncs() crashing within Py_Finalize() when using multiple interpreters.

Roundup Robot devn...@psf.upfronthosting.co.za added the comment: New changeset eb47af6e9e22 by Antoine Pitrou in branch '3.2': Test running of code in a sub-interpreter http://hg.python.org/cpython/rev/eb47af6e9e22 New changeset a108818aaa0d by Antoine Pitrou in branch 'default': Test running

[issue6531] atexit_callfuncs() crashing within Py_Finalize() when using multiple interpreters.

Antoine Pitrou pit...@free.fr added the comment: Here is a patch for subinterp-wise atexit functions. (I haven't got any specific test for the crash but the patch adds a test and it works) -- keywords: +patch stage: - patch review Added file:

[issue6531] atexit_callfuncs() crashing within Py_Finalize() when using multiple interpreters.

Changes by Christian Häggström paj...@kalvdans.no-ip.org: -- nosy: +chn ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6531 ___ ___

[issue6531] atexit_callfuncs() crashing within Py_Finalize() when using multiple interpreters.

Antoine Pitrou pit...@free.fr added the comment: There seem to be two issues at play here: - the atexit module (and its companion helper _Py_PyAtExit()) doesn't know about sub-interpreters. - PyState_FindModule() doesn't know about sub-interpreters either, because the m_index field (which

[issue6531] atexit_callfuncs() crashing within Py_Finalize() when using multiple interpreters.

Antoine Pitrou pit...@free.fr added the comment: Hmm, it seems I may be mistaken about the second point. m_index is actually generated such that all modules end up in the same position in the interpreters' respective modules_by_index lists. Sorry. --

[issue6531] atexit_callfuncs() crashing within Py_Finalize() when using multiple interpreters.

Changes by Eric Snow ericsnowcurren...@gmail.com: -- nosy: +eric.snow ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6531 ___ ___ Python-bugs-list

[issue6531] atexit_callfuncs() crashing within Py_Finalize() when using multiple interpreters.

Terry J. Reedy tjre...@udel.edu added the comment: What did you mean by 'crash'? An exception or a segfault or equivalent? I believe the finalization code was reworked a bit last fall, so could you determine whether or not there is still a problem in 3.2.1? Do not bother with 3.1.4 unless you

[issue6531] atexit_callfuncs() crashing within Py_Finalize() when using multiple interpreters.

Graham Dumpleton graham.dumple...@gmail.com added the comment: Segmentation fault. The original description explains the problem is dereferencing of a NULL pointer which has a tendency to invoke such behaviour. -- ___ Python tracker

[issue6531] atexit_callfuncs() crashing within Py_Finalize() when using multiple interpreters.

New submission from Graham Dumpleton graham.dumple...@gmail.com: I am seeing a crash within Py_Finalize() with Python 3.0 in mod_wsgi. It looks like the patches for issue-4200 were not adequate and that this wasn't picked up at the time. This new problem I am seeing looks like it may be

[issue6531] atexit_callfuncs() crashing within Py_Finalize() when using multiple interpreters.

R. David Murray rdmur...@bitdance.com added the comment: I strongly recommend you move to 3.1. 3.0 will not be getting any more bug patches. -- nosy: +r.david.murray ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue6531

[issue6531] atexit_callfuncs() crashing within Py_Finalize() when using multiple interpreters.

Graham Dumpleton graham.dumple...@gmail.com added the comment: As a provider of software that others use I am just making mod_wsgi usable with everything so users can use whatever they want. You telling me to use Python 3.1 isn't going to stop people from using Python 3.0 if that is what they

[issue6531] atexit_callfuncs() crashing within Py_Finalize() when using multiple interpreters.

R. David Murray rdmur...@bitdance.com added the comment: I'm sorry, I wasn't clear. We are recommending that no one use Python 3.0 for production. Python 3.1 fixed some significant performance issues. We are hoping that distribution packagers will not ship 3.0, but will ship 3.1 instead. But