All of lore.kernel.org
 help / color / mirror / Atom feed
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

             reply	other threads:[~2022-02-23 14:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-23 14:38 zhenyu.ren via lttng-dev [this message]
2022-02-23 15:08 ` [lttng-dev] 回复： shm leak in traced application? zhenyu.ren via lttng-dev
2022-02-25  4:47   ` [lttng-dev] 回复： " zhenyu.ren via lttng-dev
2022-02-25 14:21     ` Jonathan Rajotte-Julien via lttng-dev
2022-03-08  5:18       ` [lttng-dev] 回复： " zhenyu.ren via lttng-dev
2022-03-08 15:17         ` Mathieu Desnoyers via lttng-dev
2022-03-09  1:29           ` [lttng-dev] 回复： " zhenyu.ren via lttng-dev
2022-03-09 16:37             ` Mathieu Desnoyers via lttng-dev
2022-03-09 17:07               ` Mathieu Desnoyers via lttng-dev
2022-03-10  3:19               ` [lttng-dev] 回复：回复： " zhenyu.ren via lttng-dev
2022-03-10  4:24                 ` [lttng-dev] 回复： " zhenyu.ren via lttng-dev
2022-03-10 14:31                   ` Mathieu Desnoyers via lttng-dev
2022-03-11  2:08                     ` [lttng-dev] 回复：回复： " zhenyu.ren via lttng-dev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e706d6c8-edea-4f26-a9e2-4a66f067204e.zhenyu.ren@aliyun.com \
    --to=lttng-dev@lists.lttng.org \
    --cc=zhenyu.ren@aliyun.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.