Bug#765870: systemd-logind brings system to knees with RAM consumption

[Michael Biebl]

Am 18.10.2014 um 21:49 schrieb John Goerzen:
> Package: systemd
> Version: 215-5+b1
> Severity: grave
> Justification: renders package unusable
> 
> On investigating why my 8GB system, which was suddenly running extremely
> slow and maxed out on swap, I discovered numerous systemd-logind
> processes hogging RAM.  Specifically, 41 processes using 4278148KB (or
> roughly 4GB) of RAM.
> 
> Here is some output from top:
> 

As John told me on IRC: He is running systemd-logind under systemd-shim
on this particular system.
On other systems, where systemd is PID 1 he does not experience this issue.
I told him to find out the current running systemd-logind process which
owns the org.freedesktop.login1 D-Bus name via
"dbus-send --system --dest=org.freedesktop.DBus --print-reply
/org/freedesktop/DBus org.freedesktop.DBus.GetConnectionUnixProcessID
string:org.freedesktop.login1"

and monitor that process via strace while periodically checking with the
above command, when logind drops off the bus. So we can eventually see
from the strace what happens at that time.

Unfortunately, when stracing the process, John is no longer able to
reproduce the issue, as he told on IRC.

John, to narrow down the problem, could you please boot with
init=/bin/systemd to verify if this issue is indeed related to systemd-shim.

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-systemd-maintainers/attachments/20141104/5f41c71c/attachment.sig>