kernel-packages team mailing list archive

[James Hunt <1235649@xxxxxxxxxxxxxxxxxx>]

This problem can now be demonstrated with a single connection to upstart
that makes the following calls:

dbus_connection_open()
nih_dbus_proxy_new ()

The problem is not seen if the app instead calls:

           - nih_dbus_connect (upstart_session, disconnect_handler)
           - nih_dbus_proxy_new ()
           - nih_main_loop()

Or,

           - nih_dbus_connect (upstart_session, NULL)
           - nih_dbus_proxy_new ()
           - nih_main_loop()

Specifically, the problem appears to be that when an app calls
dbus_connection_open(), one or more of the functions in nih_dbus_setup()
should be being called to allow libdbus to interrupt the apps main loop
and request callbacks are run to clean up resources.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1235649

Title:
  uevent spam causes 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