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

[Jean-Baptiste Lallement]

Le 07/10/2013 11:12, James Hunt a écrit :
> I don't have a maguro device so debugging is going to have to be by
> proxy :)
>
> A few questions:
>
> 1) Does this only occur when the system is read-only?
No. init leaks the same amount of memory when the file system is RO or RW.

> 2) Are logs growning fast in ~/.cache/upstart/ ?
No. The biggest log file is application-legacy-dialer-app-.log (the 
application I used for the test) and it is around 700kB. The size is 
approximately the same with Mir or SF and in RO or RW mode. (ls -lSr 
/home/phablet/.cache/upstart attached)

> 3) What is the screen doing when it is on? Is it enough to run "powerd-cli display on" to see the issue?
In my test, I was launching/stopping dialer app, so the screen was 
switching between the dialer and the application scope.

Running powerd-cli or not doesn't make a difference (excepted that I 
have to tap the screen regularly to keep the display alive without 
powerd-cli :))

> 4) Is the issue seen on any other hardware?
Reproduced on maguro and mako

> Please could you:
>
> a) Run the Session Init in debug mode by adding '--debug' to 'init --user' in /usr/bin/ubuntu-touch-session.
> b) attach ~/.xsession-errors
> c) Get an strace of the Session Init.
In progress


-- 
Jean-Baptiste
irc: jibel


** Attachment added: "ls-lSr_cache_upstart.mir.ro.log"
   https://bugs.launchpad.net/bugs/1235649/+attachment/3863971/+files/ls-lSr_cache_upstart.mir.ro.log

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