[systemd-bugs] [Bug 62650] New: systemd-coredump maintains the dump in memory
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Fri Mar 22 10:51:15 PDT 2013
https://bugs.freedesktop.org/show_bug.cgi?id=62650
Priority: medium
Bug ID: 62650
Assignee: systemd-bugs at lists.freedesktop.org
Summary: systemd-coredump maintains the dump in memory
QA Contact: systemd-bugs at lists.freedesktop.org
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: pareshverma007 at gmail.com
Hardware: x86-64 (AMD64)
Status: NEW
Version: unspecified
Component: general
Product: systemd
Hi,
Often I have found multiple systemd-coredump running, occupying huge memory. I
presume that systemd-coredump is meant for handling the dumps of crashed
processes, but why does it need to keep them persistently in memory. They have
to be manually killed (I allowed them to stay in memory for quite some time to
be sure of this).
Other users are also facing the same issue as mentioned in
https://bbs.archlinux.org/viewtopic.php?pid=1247900
For now I have disabled the coredump. If required I could post the steps to
reproduce the error (however I feel crashing a process should be sufficient)
Please clarify if this is a config issue or is something wrong at our end.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20130322/3b4aac5c/attachment-0001.html>
More information about the systemd-bugs
mailing list