[lttng-dev] 回复: shm leak in traced application?

zhenyu.ren zhenyu.ren at aliyun.com
Wed Feb 23 10:08:31 EST 2022


>"I found these items also exist in a traced application which is a long-time running daemon"
 Even if lttng-sessiond has been killed!!

Thanks
zhenyu.ren
------------------------------------------------------------------
发件人:zhenyu.ren via lttng-dev <lttng-dev at lists.lttng.org>
发送时间:2022年2月23日(星期三) 22:44
收件人:lttng-dev <lttng-dev at lists.lttng.org>
主 题:[lttng-dev] shm leak in traced application?

Hi, 
   There are many items such as "/dev/shm/ust-shm-consumer-81132 (deleted)" exist in lttng-sessiond fd spaces. I know it is the result of shm_open() and shm_unlnik() in create_posix_shm(). 
   However, today, I found these items also exist in a traced application which is a long-time running daemon. The most important thing I found is that there seems no reliable way to release share memory.
   I tried to kill lttng-sessiond but not always release share memory. Sometimes I need to kill the traced application to free share memory....But it is not a good idea to kill these applications.
   My questions are: 
   1. Is there any way to release share memory without killing any traced application?
   2. Is it normal that many items such as "/dev/shm/ust-shm-consumer-81132 (deleted)" exist in the traced application?

Thanks
zhenyu.ren

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.lttng.org/pipermail/lttng-dev/attachments/20220223/a13703a7/attachment.htm>


More information about the lttng-dev mailing list