https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255445
--- Comment #14 from Victor Stinner ---
Using the script of Comment 2, I cannot reproduce the hang with Python 3.9.4 on
FreeBSD 13. I used:
for i in $(seq 1 100); do python3.9 script.py || break; done
--
You are receiving this mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255445
--- Comment #15 from yocal...@gmail.com ---
(In reply to Victor Stinner from comment #14)
Hi Victor, thanks for testing it out. Your results are expected since the 2
commits that fix the problem were included with python3.9. Have you
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255445
--- Comment #17 from Victor Stinner ---
Backporting "bpo-19466: Py_Finalize() clears daemon threads earlier (GH-18848)"
sounds dangerous. This fix relies on many other fixes. Without the other fixes,
clearing daemon threads earlier can
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255445
--- Comment #18 from yocal...@gmail.com ---
(In reply to Victor Stinner from comment #17)
Thanks for the tips and the links to your notes. However, the panics are still
happening on py3.9.4. Unfortunately, I've analyzed 11 core dumps at
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=255445
--- Comment #16 from Victor Stinner ---
I can reproduce the issue with Python 3.8 on Linux.
Well, first, don't rely on implicit resource management: don't rely on
__del__() destructor.
You should use "with pool:" and then call
