Follow-up Comment #1, bug #93616 (project xrootd):
It's important to understand that there is a pool of pre-read threads that
are shared by file objects that have enabled pre-reads. So, it is normal to
see pre-read threads waiting for work. Once a pre-read thread has been
dispatched to pre-read data for a file then that file object cannot be
deleted until the pre-read completes (mostly because we can't cancel threads
if they are within XrdClient). What the traceback shows is that a pre-read
was dispatched against the file just at the moment it was being deleted and
it looks like a deadlock occurred. This appears to happen because an
exclusive lock is prematurely obtained in the destructor which causes the
pre-read thread, should it just be started, to hang and never terminate the
preread on the object being destroyed. The fix is now in git head. Could you
see if this fixes the problem?
_______________________________________________________
Reply to this item at:
<http://savannah.cern.ch/bugs/?93616>
_______________________________________________
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
