AFAICT, and probably stating the obvious, every thread except 2 was waiting for the GIL. Thread 2 was starting a thread and waiting on a lock to delete the current GIL state pointer. Looks like a Python or OS bug to me.
AFAICT, and probably stating the obvious, every thread except 2 was waiting for the GIL. Thread 2 was starting a thread and waiting on a lock to delete the current GIL state pointer. Looks like a Python or OS bug to me.