kernel-packages team mailing list archive

[Steve Langasek <steve.langasek@xxxxxxxxxxxxx>]

I've tested on a mako device here, and the memory usage is not all due
to a misbehaved client.  I've tracked down all the clients of the
session init; unity8 is the only long-lived client other than the
bridges, and if I kill unity8 and let it respawn, upstart gains back
some of the memory, but *not all*: if I feed events into the session
init, bringing its memory usage up to 93.3MB, and then kill unity8 (and,
in fact,if I go through one-by-one and kill *all* the processes related
to the session), upstart frees *some* memory, but its total usage
remains at 88MB - compared to 5MB when it starts out.

Another thing I've found out, though, is that if I force a re-exec of
the session init with 'telinit u', the memory usage drops down... and
never rises again, even if I spam it with more events.  This suggests a
possible workaround of just re-execing the session init immediately
after startup.  But that probably requires landing a fix for bug
#1238078 first.

-- 
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 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