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
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/ ? legacy- dialer- app-.log (the .cache/ upstart attached)
No. The biggest log file is application-
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/
> 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: ubuntu- touch-session.
>
> a) Run the Session Init in debug mode by adding '--debug' to 'init --user' in /usr/bin/
> b) attach ~/.xsession-errors
> c) Get an strace of the Session Init.
In progress
--
Jean-Baptiste
irc: jibel