Program aborted by allocation failed when running after 30min. about blazesym

[ThinkerYzu1]

I am curious about how much memory it uses. Are there any memory leaks in the library? Could you provide details of the process? For example, VSZ/USS/RSS.

By the way, could you give me some background about this process if possible? Is it a long-running process to do symbolization? How many libraries and sizes would be? I mean, do you believe it just uses up all memory or just leaks?

[ThinkerYzu1]

I just made a patch to give the caller a chance to handle it. However, according to the manual, the allocator may abort without a return. Please check the patch if you can reproduce it.

We don't have a way to release specific ELF from memory except free the whole symbolizer. From the C API point of view, it should call blazesym_free() to free the whole symbolizer, and create a new one.

[woodpenker]

I just made a patch to give the caller a chance to handle it. However, according to the manual, the allocator may abort without a return. Please check the patch if you can reproduce it.

Sorry for the delay in getting back to you. I can't reproduce it every time, so this is just a guess, I will let you know if it happens again with this fix.

We don't have a way to release specific ELF from memory except free the whole symbolizer. From the C API point of view, it should call blazesym_free() to free the whole symbolizer, and create a new one.

Thanks for the advice, I call blazesym_free() only when the whole program exit like this, The symbolizer is a global var, is that correct?

[ThinkerYzu1]

Sorry for the delay in getting back to you. I can't reproduce it every time, so this is just a guess, I will let you know if it happens again with this fix.
No worries! Thank you for reporting this issue.

Thanks for the advice, I call blazesym_free() only when the whole program exit like this, The symbolizer is a global var, is that correct?
Symbolizer is not a global variable. you may have multiple instances with different features enabled or for different threads.

[woodpenker]

Sorry for the delay in getting back to you. I can't reproduce it every time, so this is just a guess, I will let you know if it happens again with this fix.
No worries! Thank you for reporting this issue.
Thanks for the advice, I call blazesym_free() only when the whole program exit like this, The symbolizer is a global var, is that correct?
Symbolizer is not a global variable. you may have multiple instances with different features enabled or for different threads.

Finally, we found the root cause of the mem leak, it was NOT due to blazesym but some code dependency we wrote. Sorry for making so much noise here. And thanks again for the enhancement of this wonderful lib!