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 eric.snow
Recipients eric.snow
Date 2019-03-29.20:38:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Among the first 3 things that happen in Py_FinalizeEx() are, in order:

1. wait for all non-daemon threads (of the main interpreter) to finish
2. call registered atexit funcs
3. mark the runtime as finalizing

At that point the only remaining Python threads are:

* the main thread (where finalization is happening)
* daemon threads
* non-daemon threads created in atexit functions
* any threads belonging to subinterpreters

The next time any of those threads (aside from main) acquire the GIL, we expect that they will exit via a call to PyThread_exit_thread() (caveat: issue #36475).  However, we have no guarantee on when that will happen, if ever.  Such lingering threads can cause problems, including crashes and deadlock (see issue #36469).

I don't know what else we can do, beyond what we're already doing.  Any ideas?
Date User Action Args
2019-03-29 20:38:26eric.snowsetrecipients: + eric.snow
2019-03-29 20:38:26eric.snowsetmessageid: <>
2019-03-29 20:38:26eric.snowlinkissue36476 messages
2019-03-29 20:38:26eric.snowcreate