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

Jean-Baptiste Lallement jean-baptiste at ubuntu.com
Sun Oct 6 09:08:29 UTC 2013


I confirm this behaviour with build 82 on mako.
To illustrate it I made the following test:
Start and stop dialer-app every 6s (reasonable delay to give time to the application to start and stop)
The application is started with: start application APP_ID=dialer-app
and stop with a kill.

I captured RSS measured by ps after each stop and made 2 runs with Mir and 1 with SF. The result is attached.
I shows that RSS usage of init with Mir is much higher the SF and growth is exponential while it is linear with Mir.

As a side note, the number of samples with Mir is limited to less than
50 because the phone stops responding at this moment while it continues
to run fine with SF. This is reproduceable.

** Attachment added: "RSS-usage-Mir_vs_SF.png"
   https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1235649/+attachment/3862180/+files/RSS-usage-Mir_vs_SF.png

** Also affects: upstart (Ubuntu Saucy)
   Importance: Critical
       Status: Confirmed

** Tags added: qa-manual-testing qa-touch rls-s-incoming

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

Title:
  session upstart leaks massive amounts of memory on Ubuntu Touch

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

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/ubuntu/+source/upstart/+bug/1235649/+subscriptions



More information about the foundations-bugs mailing list