definitely not fixed in unity-mir yet ... this will need serious reworking of
the lifecycle management. I don't know why but i can not change anything on
this bug anymore, david, can you set unity-mir back to confirmed ?
(we worked around the issue with a hack in upstart-app-launch and did not f
** Changed in: unity-mir
Status: Confirmed => Fix Released
** Changed in: webbrowser-app (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1303676
sooo ...
using a combination of:
https://code.launchpad.net/~abreu-alexandre/webbrowser-app/better-control-webengine-lib-loaded/+merge/215280
and the hack from:
https://code.launchpad.net/~ted/upstart-app-launch/process-group-kill/+merge/215475
gets the issue solved, but ... the webapp (re-)start
As Chris pointed out in comment #31, upstart's use of setsid() means
that, by default, all processes of a launched application are in the
same session and process group. This process group is orphaned from the
start so the kernel does not send SIGHUP/SIGCONT signals when, for
example, webbrowser-ap
Following on from Jamie's comments, I'm just going to braindump what
else we discovered is happening yesterday:
1) appmgr sends SIGSTOP to the process group for the webapp-container
2) The low memory killer comes along and kills the process group leader
3) appmgr considers the app closed, and neve
To clearly state the issue:
1. the leader of the process group for the app using oxide is sent STOP by the
Unity appmgr (application lifecycle). Because the app is started via upstart,
the appmgr sends SIGSTOP to -, ie the process group and the process group
leader and all children (ie, the oxid
"2. appmgr is not cleaning up the killed processes" should have read:
2. appmgr is not cleaning up all the stopped processes when a process in
the process group is killed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
All processes we spawn quit when their IPC links to the browser are
closed (ie, the browser process being killed). This works ok in my
testing here. The process tree in comment 25 shows that all of our child
processes have been *stopped* (by somebody sending them SIGSTOP). I
don't see how I can mak
one other thing i noticed is that if you close a webapp via the hud
close action, all attached oxide processes get killed properly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1303676
Title:
[weba
After the call with ricmm, and with ogra's process tree in front of us:
proposed solution for now: have oxide kill itself if the parent process dies
alternative: figure out why the process group is apparently not formed
if both webapp-container and oxide were in the same process group, then the
sy
with the latest changes in image 286 i can now start 6 webapps and their
thubnails stay in the UI ...
switching through them for a while with the right edge gesture they
start dieing and respawning (which gets the app selector completely out
of order and you most of the time do not end up with the
** Changed in: unity-mir
Status: Triaged => Incomplete
** Changed in: unity-mir
Assignee: Daniel d'Andrada (dandrader) => (unassigned)
** Changed in: unity-mir
Importance: High => Undecided
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Why is it a unity-mir bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1303676
Title:
[webapp-container] when using multiple webapps they crash randomly, if
there is only one app remaining, this
** Tags added: qa-touch-blocker
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1303676
Title:
[webapp-container] when using multiple webapps they crash randomly, if
there is only one app remaining,
The oxide portion of this is bug #1304648.
** Changed in: oxide
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1303676
Title:
[webapp-container] when using multipl
** Changed in: unity-mir
Assignee: (unassigned) => Daniel d'Andrada (dandrader)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1303676
Title:
[webapp-container] when using multiple webapps they
For the specific sandbox IPC helper process issue, see bug 1304648
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1303676
Title:
[webapp-container] when using multiple webapps they crash randomly, if
Re-opening on webbrowser-app (ie container) as it seems we're using more
memory that before, and the OOM killer removes webapps more quickly.
Some observations though:
- the situation gets worse when mixing old and new webapps, because we have
both the oxide runtime in memory and the old qtwebkit
** Tags added: webapps-blocker
** Tags removed: webapps-blocker
** Tags added: webapps-hotlist
** Changed in: webbrowser-app (Ubuntu)
Status: Invalid => Confirmed
** Also affects: oxide
Importance: Undecided
Status: New
--
You received this bug notification because you are a m
That looks expected. Chromium forks the browser process to use it as a
sandbox IPC process, which is great for Chromium (because it forks it at
startup and before any threads are created) but sucks for us (because by
the time it forks, we already have a QML app and other gunk).
I'm trying to reimp
On second thought, there seems to be something fishy:
$ initctl status application-click
APP_ID=net.launchpad.click-webapps.googleplus_googleplus_6
application-click (net.launchpad.click-webapps.googleplus_googleplus_6)
start/running, process 8105
phablet@ubuntu-phablet:~$ ps aux | grep google
p
@Oliver: the kill signal was probably sent to the renderer process, the
one that would be consuming too much memory, which left the
browser/container executable running, but without a renderer.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
intrestingly the processlist still has the apps ... so i assume only
some subprocess died
2679 ?T 0:00 webapp-container --enable-back-forward
--webappUrlPatterns=https://plus.google.*/*,https://accounts.google.*/*
https://plus.google.com
3330 ?T 0:00 webapp-container
i see teh following in syslog ... which indicates that OOM kicked in (i
had 6 apps open of which 4 died over time):
root@ubuntu-phablet:~# grep "send sigkill" /var/log/syslog
Apr 8 13:14:58 ubuntu-phablet kernel: [ 1369.711399] send sigkill to 3839
(webapp-containe), adj 798, size 23128
Apr 8 1
** Project changed: unity8 => unity-mir
** Changed in: unity-mir
Status: New => Triaged
** Changed in: unity-mir
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/
The apps are not crashing. I can confirm while still testing on #281
that all of the webapp-container and oxide-renderer processes are
present and alive (or paused) for all of the 10 webapps I have started.
At some random point they stop being displayed on the 'Apps' list in
Unity.
** Changed in:
i can confirm that there are a bunch of webapp-container processes in my
processlist even though there is only one app on screen ...
i also notice that there are as many zombie processes of:
[oxide-renderer]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@Oliver: can you confirm what Alan is seeing, that the apps are actually
running, but not visible in the apps scope in unity?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1303676
Title:
[webapp-con
I just tried again, and when I hit the 4th app they all start failing so I now
have one.
However, in the process list I still see them, they just disappear from unity.
phablet 4922 0.0 0.8 232980 15232 ?T13:13 0:00
webapp-container --enable-back-forward
--webappUrlPatterns=htt
** Summary changed:
- [webapp-container] webapps seem to randomly be replaced after a while with
another webapp or die
+ [webapp-container] when using multiple webapps they crash randomly, if there
is only one app remaining, this one starts being replaced when new ones start
--
You received th
30 matches
Mail list logo
