Follow-up Comment #4, bug #99083 (project xrootd): Hi Andy, I just tried again, and the problem is still there - valgrind says the same thing (except that the line number in XrdSysIOEvents.cc is now 620). Here's a link to the code I'm using: https://github.com/jussy/xrootd-latency-test There's a file in there with a list of hosts, one of which is down (lxfsre03a07.cern.ch). The problem happens when the network comes back with "connection refused" or "no route to host". You might need to run it a few times to reproduce the problem. Run it like this: xrd-latency-test -v -p / src/node.cms.list and eventually you should see it in valgrind. Cheers, Justin _______________________________________________________ Reply to this item at: <http://savannah.cern.ch/bugs/?99083> _______________________________________________ Message sent via/by LCG Savannah http://savannah.cern.ch/ ######################################################################## Use REPLY-ALL to reply to list To unsubscribe from the XROOTD-DEV list, click the following link: https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1