We consider this a false positive. Many plugin allocate storage for the life of the plugin. As there is no way of exiting xrootd other than killing it, the storage is obviously freed when the process dies. While we can go and fix all of these one-time allocations that's a lot of work to simply satisfy memory leak detectors when, in practice, there really is no leak. Yes, I'm sure several people will disagree but we're taking the path of least resistance here.

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

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/1008?email_source=notifications\u0026email_token=AA7NRDWLBUOVNY6WV5HUIDDP5P7WLA5CNFSM4HZQ5KA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZDAFYA#issuecomment-507904736", "url": "https://github.com/xrootd/xrootd/issues/1008?email_source=notifications\u0026email_token=AA7NRDWLBUOVNY6WV5HUIDDP5P7WLA5CNFSM4HZQ5KA2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZDAFYA#issuecomment-507904736", "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