← Back to team overview

kernel-packages team mailing list archive

[Bug 1235649] Re: session upstart leaks massive amounts of memory on Ubuntu Touch


jibel - thanks. It does indeed look like bug 1234743 as the trace shows
a lot of the following events:


This would explain the Session consuming a lot of CPU since those events
are generated by the kernel, picked up by the upstart-udev-bridge which
injects them into the system init event space. These events are then
noticed by the upstart-event-bridge running as phablet and injected into
the Session Init with the ":sys:" prefix.

Could you run that again as "strace -fFttv -s 1024 ..." so we can see
some timestamps?

Also, please attach /var/log/udev and the output of 'ls -al

Adding kernel since as this issue only affects particular hardward, it
is highly unlikely to be an Upstart issue.

** Also affects: linux (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: upstart (Ubuntu Saucy)
       Status: Confirmed => Incomplete

You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.

  session upstart leaks massive amounts of memory on Ubuntu Touch

Status in “linux” package in Ubuntu:
Status in “upstart” package in Ubuntu:
Status in “linux” source package in Saucy:
Status in “upstart” source package in Saucy:

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: