Davin Potts added the comment:
At nearly 5 years of age, this issue unfortunately never saw a viable
demonstration of how to provoke the reported behavior. Hopefully the reporter
either (1) discovered the nature of the problem originated elsewhere and he was
able to quickly fix it, or (2)
Ezio Melotti added the comment:
Can you still reproduce the issue?
--
nosy: +ezio.melotti
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8144
___
Ask Solem a...@opera.com added the comment:
Did you finish the code to reproduce the problem?
--
nosy: +asksol
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8144
___
New submission from brandon drr...@gmail.com:
Multiprocessing goes into an infinite loop during shutdown, trying to connect
to a remote queue - I *think* during finalization.
The actual loop appears to be the while(1) in connection.py line 251, and I
think it is being called initially from
Changes by Benjamin Peterson benja...@python.org:
--
assignee: - jnoller
nosy: +jnoller
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue8144
___
brandon drr...@gmail.com added the comment:
After getting into the infinite loop, here's exception from CTRL-C (posted just
to show stack trace -- i am still working on getting come sample code together
-- meant to show it is infact in that while(1) a 251 in connection.py):
KeyboardInterrupt
