Manu Cupcic added the comment:
Hi,
Antoine, thank you for the patch you proposed. It indeed fixed the bug I was
seeing (I ran a job that usually crashes in one to two hours over the week end
and it is still running).
I am not sure what we should do now. Can this patch be integrated
Manu Cupcic added the comment:
I am testing this patch right now. Will report back.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue13992
Manu Cupcic added the comment:
I am also hitting this issue.
I have been able to reproduce it in python 2.5 and 2.7, on debian 6 (64 bits)
Exactly like the reporter, I am making extensive use of threads. I am also
using SQLalchemy.
All my threads but one are waiting (probably for the GIL
Manu Cupcic added the comment:
(gdb) p op
$12 = (PyObject *) 0x4dc7bc0
thread all apply bt is going to be very long no ? Could you tell me what you
want to know that is not in info threads maybe ? I can definitely post it here,
but it's going to be a lot of output.
I can be available on IRC
