[lttng-dev] shm leak in traced application? - zhenyu.ren via lttng-dev

From: "zhenyu.ren via lttng-dev" <lttng-dev@lists.lttng.org>
To: "lttng-dev" <lttng-dev@lists.lttng.org>
Subject: [lttng-dev] shm leak in traced application?
Date: Wed, 23 Feb 2022 22:38:50 +0800	[thread overview]
Message-ID: <e706d6c8-edea-4f26-a9e2-4a66f067204e.zhenyu.ren@aliyun.com> (raw)

[-- Attachment #1.1: Type: text/plain, Size: 844 bytes --]

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

[-- Attachment #1.2: Type: text/html, Size: 4190 bytes --]

[-- Attachment #2: Type: text/plain, Size: 156 bytes --]

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev