dx-packages team mailing list archive
-
dx-packages team
-
Mailing list archive
-
Message #03325
[Bug 1235649] Re: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch
So the reason the memory usage wasn't growing after re-exec was because
unity8 didn't automatically reconnect when the dbus connection dropped.
If I kill and restart unity8, the problem reappears.
So the memory usage is indeed associated with the dbus client, even
though disconnecting the client doesn't free the memory, and valgrind
doesn't consider the memory to have been lost.
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to unity in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1235649
Title:
uevent spam causes libdbus client code in session upstart to consume
massive amounts of memory on Ubuntu Touch
Status in Upstart:
New
Status in “linux” package in Ubuntu:
Invalid
Status in “systemd” package in Ubuntu:
New
Status in “unity” package in Ubuntu:
New
Status in “upstart” package in Ubuntu:
Fix Released
Status in “linux” source package in Saucy:
Invalid
Status in “systemd” source package in Saucy:
New
Status in “unity” source package in Saucy:
New
Status in “upstart” source package in Saucy:
Fix Released
Bug description:
using ubuntu touch image 82 i see the session init consume about 10MB per minute as long as the screen is on with Mir.
running the same session with surfaceflinger only consumes 1MB per minute.
in both cases the system starts to swap heavily at some point, making
the UI unresponsive.
http://paste.ubuntu.com/6196223/ has the top output of a Mir session
after 30min, the UI just got completely unresponsive when this
snapshot was taken.
http://paste.ubuntu.com/6196332/ is the top output of a surfaceflinger
session where the screen was off for about 10min
apparently the leak only occurs while the screen is on, it seems to be
permanently there but in the case of surfaceflinger it hits less hard.
To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/1235649/+subscriptions