Hi Bastian, Thanks for reporting this issue. Just to clarify, this scenario happens after the xrootd client lib has been unloaded, right? I assume so because the DefaultEnv has been finalized. If so there is really not much we can do about it. I will add an 'if' guard to FileStateHandler, but if the dlclose really unloads the lib (not only decrement the reference counter) you will get a segfaul anyway, right? Could please test if my last commit fixes this issue: https://github.com/xrootd/xrootd/commit/7bfa28435a70b71257e0defa239ff963f6e0fc39 Please let me know so I can include this in 4.5.0. Cheers, Michal -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/xrootd/xrootd/issues/433#issuecomment-259720711 ######################################################################## 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