This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author pitrou
Recipients benjamin.peterson, gregory.p.smith, jnoller, jon, kristjan.jonsson, pitrou, r.david.murray
Date 2009-11-13.19:04:46
SpamBayes Score 0.000606631
Marked as misclassified No
Message-id <1258139088.15.0.354485050055.issue7060@psf.upfronthosting.co.za>
In-reply-to
Content
Ok, the problem is that a finalizer calls _decref which tries to open an
XMLRPC connection (!) to an address on which nobody listens anymore.
Then stupid SocketClient (in multiprocessing.connection) loops endlessly
because it is designed to do so when it gets ECONNREFUSED.

(when you Ctrl-C, you don't see all this because it happens in a
finalizer, and only a terse message is displayed)

So there are two problems:
- why does test_multiprocessing think it should open an XMLRPC
connection to a closed endpoint
- why doesn't SocketClient have some kind of timeout rather than looping
stupidly
History
Date User Action Args
2009-11-13 19:04:48pitrousetrecipients: + pitrou, gregory.p.smith, kristjan.jonsson, jon, benjamin.peterson, jnoller, r.david.murray
2009-11-13 19:04:48pitrousetmessageid: <1258139088.15.0.354485050055.issue7060@psf.upfronthosting.co.za>
2009-11-13 19:04:46pitroulinkissue7060 messages
2009-11-13 19:04:46pitroucreate