Hi @simonmichal I've realised that there are some paths where the read event action (e.g. OnReadTimeout) can cause the AsyncSocketHandler to be not only closed but destroyed too. So this patch does nothing to help in those cases (and adds at least one access to invalid memory); so I'd propose to abandon/close this PR. I will look for another solution.

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/pull/1935#issuecomment-1450465404", "url": "https://github.com/xrootd/xrootd/pull/1935#issuecomment-1450465404", "name": "View Pull Request" }, "description": "View this Pull Request 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