Hi @amadio,
As discussed privately, we noticed that one headnode of the EOSLHCb instance had its memory usage increasing.
After enabling jemalloc profiling on the headnode, I managed to produce the following outputs:
I believe the memory leaks come from the GSI authentication and non-freed cryptossl objects?
Thanks in advance :)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
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