touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #07455
[Bug 1235649] Re: uevent spam causes libdbus client code in session upstart to consume massive amounts of memory on Ubuntu Touch
** Changed in: unity (Ubuntu Saucy)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity in Ubuntu.
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 Touch Landing Plan:
Fix Released
Status in Unity:
Confirmed
Status in Upstart:
Fix Released
Status in “linux” package in Ubuntu:
Invalid
Status in “systemd” package in Ubuntu:
Invalid
Status in “unity” package in Ubuntu:
Confirmed
Status in “upstart” package in Ubuntu:
Fix Released
Status in “linux” source package in Saucy:
Invalid
Status in “systemd” source package in Saucy:
Invalid
Status in “unity” source package in Saucy:
Invalid
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/landing-plan/+bug/1235649/+subscriptions