STINNER Victor <vstin...@python.org> added the comment:
I believe that this issue cannot occur in Python 3.8 thanks for bpo-36475. According to the backtrace, a thread does crash in PyEval_EvalFrameEx(). I understand that it's a daemon thread. To execute PyEval_EvalFrameEx(), a daemon thread must hold the GIL. With bpo-36475, a daemon thread now exits immediately instead of taking the GIL. ---------- nosy: +vstinner resolution: -> fixed stage: -> resolved status: open -> closed superseder: -> PyEval_AcquireLock() and PyEval_AcquireThread() do not handle runtime finalization properly. _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue23592> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
