Print

Print

Well, based on the information in the ticket it looks like it's unlikely to fix the problem. Then again, the ticket is pretty sparse on what you discovered during debugging. The issue seems to be that a either a lock is not released when it is supposed to be and deadlock occurs. I don't see in the information here any detection of which thread was holding the lock that caused the deadlock. The information is there but it appears no one actually tracked it down to what the active lock holder is actually doing at the time. Maybe that was done but it's not reflected in the ticket. So, if the task has already been deleted by the task manager why has the lock not been released?, I don't see how moving the the Invalidate() call in the destructor addresses that problem.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: <xrootd/xrootd/issues/1883/1439590743@github.com>

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1883#issuecomment-1439590743", "url": "https://github.com/xrootd/xrootd/issues/1883#issuecomment-1439590743", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

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