** Also affects: systemd (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- session upstart leaks massive amounts of memory on Ubuntu Touch
+ uevent spam causes session upstart to consume massive amounts of memory on
Ubuntu Touch
--
You received this bug notification be
Valgrinding the session init shows that most of the memory is correctly
freed at quiesce time.
** Attachment added: "valgrind session init consuming ~250MB (with
suppressions)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1235649/+attachment/3866119/+files/valgrind-250M.log.gz
--
Yo
Valgrind run as:
valgrind -v -v -v -v --show-reachable=yes --track-origins=yes --leak-
check=full init --debug --user
** Attachment added: "valgrind session init consuming ~500MB (no suppressions)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1235649/+attachment/3866123/+files/valgri
** Changed in: upstart (Ubuntu Saucy)
Assignee: (unassigned) => James Hunt (jamesodhunt)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235649
Title:
session upstart leaks massive amounts of me
** Tags removed: rls-s-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235649
Title:
session upstart leaks massive amounts of memory on Ubuntu Touch
To manage notifications about this bug g
** Tags added: kernel-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235649
Title:
session upstart leaks massive amounts of memory on Ubuntu Touch
To manage notifications about this bug go to:
Attempting to run the script in #30 against a session init as below
*outside* of a the standard gui environment with no .conf files does not
trigger the issue:
$ mkdir -p /tmp/conf /tmp/log
$ init --debug --no-startup-event --confdir /tmp/conf --logdir /tmp/log --user
Same outcome running like th
I can no recreate the issue with memory not being freed by running:
http://paste.ubuntu.com/6205552/.
This is recreatable on i386 desktop images so although problem (1) in
#27 is h/w specific, problem (2) is not.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Could someone run the "make check" tests for the libnih package on a
mako/maguro device?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235649
Title:
session upstart leaks massive amounts of memory
To summarise: there are 2 problems here:
1) The kernel spamming userspace with udev messages on mako+maguro
(grouper doesn't appear to be affected but not independently verified
yet).
2) Upstart not releasing memory once the kernel has finished spamming
userspace (artificially forced by running "
output of "initctl list" as user phablet.
** Attachment added: "initctl_list.out"
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1235649/+attachment/3864504/+files/initctl_list.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
>From info provided by jibel...
Forcing a log flush (#25) doesn't resolve the high memory usage (as we'd
expect, but worth ruling out).
The state file in #24 looks sane to me; forcing a re-exec of the Session
Init does cause the memory to fall to reasonable levels. This almost
feels like a compil
Can someone try running "/sbin/initctl notify-disk-writeable" and see if
the session inits memory consumption drops? Alternatively, run the
session init as "init --user --debug --no-log".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
output of get_state.sh as user phablet
** Attachment added: "get_state.out"
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1235649/+attachment/3864343/+files/get_state.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
@jibel - that get_state.out appears to have either been run as root, or
atleast outside the session init environment. Please could you re-run as
user phablet?
Also, please could you attach /var/log/udev ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
i can definitely make it stop consuming more ram by stopping the
upstart-event-bridge session job.
this works on both devices.
the ram does not get freed but the consumption does not keep rising either
anymore then.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Apparently, the high cpu load stop when the upstart-event-bridge is
stopped. This lends weight to the high cpu issue being caused the a
kernel udev event issue (like bug 1234743).
However, what is not explained is why the Session Init retains the
memory it consumes once the upstart-event-bridge is
more verbose strace during a start/stop of dialer-app
** Attachment added: "strace_-fFvtt_-s.init_--user_--debug.strace.gz"
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1235649/+attachment/3864305/+files/strace_-fFvtt_-s.init_--user_--debug.strace.gz
--
You received this bug notifi
output of ls -al /proc/1467/fd/
** Attachment added: "ls_-al__proc_PID_fd_.out"
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1235649/+attachment/3864308/+files/ls_-al__proc_PID_fd_.out
** Changed in: upstart (Ubuntu Saucy)
Status: Incomplete => Confirmed
** Changed in: linux
/var/log/udev
** Attachment added: "_var_log_udev"
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1235649/+attachment/3864307/+files/_var_log_udev
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
output of get_state.sh after dialer-app has been stopped.
** Attachment added: "get_state.out"
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1235649/+attachment/3864306/+files/get_state.out
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Also, please could you run
http://people.canonical.com/~jhunt/upstart/scripts/get_state.sh as user
phablet and attach to this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235649
Title:
sessio
jibel - thanks. It does indeed look like bug 1234743 as the trace shows
a lot of the following events:
:sys:cpu-device-online
:sys:cpu-device-offline
:sys:power_supply-device-changed
This would explain the Session consuming a lot of CPU since those events
are generated by the kernel, picked up by
btw, .xession-errors shows 5 run of dialer, 1 run of shorts and 1 run of
calculator, and strace shows 1 run of dialer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235649
Title:
session upstart le
strace of session init
** Attachment added: "init_--user_--debug.strace"
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1235649/+attachment/3864101/+files/init_--user_--debug.strace
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
/home/phablet/.xsession-errors with init --user --debug
** Attachment added: "_home_phablet_.xsession-errors"
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1235649/+attachment/3864070/+files/_home_phablet_.xsession-errors
--
You received this bug notification because you are a membe
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 grownin
Answering own question (5): https://wiki.ubuntu.com/Touch/Testing/Mir
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235649
Title:
session upstart leaks massive amounts of memory on Ubuntu Touch
To
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?
2) Are logs growning fast in ~/.cache/upstart/ ?
3) What is the screen doing when it is on? Is it enough to run "powerd-cli
display on" to see the i
https://wiki.ubuntu.com/Touch/Testing/Mir
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235649
Title:
session upstart leaks massive amounts of memory on Ubuntu Touch
To manage notifications about
the growth in itself is an issue though, even SF will hit swap at some
point, just later ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235649
Title:
session upstart leaks massive amounts of mem
replace:
I shows that RSS usage of init with Mir is much higher the SF and growth is
exponential while it is linear with Mir.
by
It shows that RSS usage of init with Mir is much higher than SF and growth is
exponential while it is linear with SF.
--
You received this bug notification because y
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
i tried downgrading upstart version by version until 1.9.1-0ubuntu5
(which was the first one with user sessions enabled) and it seems all
versions expose this behavior.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
** Changed in: upstart (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235649
Title:
session upstart leaks massive amounts of memory on Ubuntu Touch
To manag
after capturing the above i tried to upgrade to upstart 1.10-0ubuntu6
from the archive which exposes the same behavior.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235649
Title:
session upstart l
both of the above was observed on maguro btw.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1235649
Title:
session upstart leaks massive amounts of memory on Ubuntu Touch
To manage notifications ab
37 matches
Mail list logo
