<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - systemd-coredump maintains the dump in memory"
href="https://bugs.freedesktop.org/show_bug.cgi?id=62650">62650</a>
</td>
</tr>
<tr>
<th>Assignee</th>
<td>systemd-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Summary</th>
<td>systemd-coredump maintains the dump in memory
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>systemd-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Reporter</th>
<td>pareshverma007@gmail.com
</td>
</tr>
<tr>
<th>Hardware</th>
<td>x86-64 (AMD64)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Component</th>
<td>general
</td>
</tr>
<tr>
<th>Product</th>
<td>systemd
</td>
</tr></table>
<p>
<div>
<pre>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
<a href="https://bbs.archlinux.org/viewtopic.php?pid=1247900">https://bbs.archlinux.org/viewtopic.php?pid=1247900</a>
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.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>