** Changed in: webbrowser-app (Ubuntu)
Assignee: Olivier Tilloy (osomon) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1478853
Title:
OOM
Actually the tuning of the memory consumption of oxide/chromium fixed
the problem.
** Changed in: canonical-devices-system-image
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
I think that, considering the age of this, we're happy with the values
today?
** Changed in: ubuntu-app-launch (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in
Lower priority based on comment #16
** Changed in: canonical-devices-system-image
Importance: Critical => High
** Changed in: canonical-devices-system-image
Milestone: ww46-2015 => backlog
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Changed in: canonical-devices-system-image
Milestone: ww40-2015 => ww46-2015
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1478853
Title:
OOM scoring kills
That last item is already recorded and tracked as bug:
https://bugs.launchpad.net/oxide/+bug/1267132
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1478853
Title:
At this stage we have a series of optimizations to deal with that
situation :
- a crash handler for webapps, which prevents the appearance of blank webviews
- https://bugs.launchpad.net/ubuntu/+source/oxide-qt/+bug/1375215
- a memory limit adjustment in Oxide -
@dbarth - i assigned to you, since i think it makes more sense, let's
sync on irc if you disagree
** Changed in: canonical-devices-system-image
Assignee: kevin gunn (kgunn72) => David Barth (dbarth)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded
** No longer affects: qtmir (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1478853
Title:
OOM scoring kills the browser's render process while the browser
QtMir relying on ubuntu-app-launch to set OOM scoring
** Changed in: qtmir (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
I don't know if this is relevant, but today I've found a URL which occurs
multiple crashes of the browser on my BQ4.5:
http://fossbytes.com/salaries-of-software-engineers-top-paying-skills-roles-and-best-engineering-schools/
after link in browser chrashes during next 5 minutest. Other URLs in
I tentatively added an oxide task to check whether oxide itself could be
tinkering with the OOM scores of its render processes.
** Also affects: oxide
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages,
** Changed in: canonical-devices-system-image
Milestone: ww34-2015 = ww40-2015
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1478853
Title:
OOM scoring kills
20921 ?Ssl0:02 webbrowser-app
20966 ?Sl 0:00 /usr/bin/python3
/usr/lib/dbus-property-service/propertyservice
20977 ?S 0:00 /usr/lib/arm-linux-gnueabihf/oxide-qt/chrome-sandbox
/usr/lib/arm-linux-gnueabihf/oxide-qt/oxide-renderer --t
20980 ?S 0:00
On Tue, 2015-08-04 at 20:43 +, Gerry Boland wrote:
You're correct the OOM score set to 2 arbitrary values. They're
hardcoded and set by upstart-app-launch. I believe your question is my
question 2 above, to which I don't have an answer.
They're not entirely arbitrary, more or less built
Ref on oom_score_adj:
https://www.kernel.org/doc/Documentation/filesystems/proc.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1478853
Title:
OOM scoring kills
You're correct the OOM score set to 2 arbitrary values. They're
hardcoded and set by upstart-app-launch. I believe your question is my
question 2 above, to which I don't have an answer.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
@greyback, it seems that upstart-app-launch just sets the score for
paused apps at 900, and changes them back to 100 after being resumed. I
wonder where these numbers came from, and how OOM Killer further
prioritizes processes with the same score. 900 seems pretty high, but I
really don't have
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: webbrowser-app (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
There's not enough information here to make a proper attack on this
issue, and this is a complex topic.
We need someone to sit down and determine things like:
1. why did the OOM killer strike a foreground app? Did it use an insane amount
of memory? If a webapp, is it a QtWebkit-based app, or
@olivier anything we can do to reduce memory consumption and/or ensure
the renderer is not doing something in the background
** Also affects: webbrowser-app (Ubuntu)
Importance: Undecided
Status: New
** Changed in: webbrowser-app (Ubuntu)
Assignee: (unassigned) = Olivier Tilloy
When in the background, the renderer process should be stopped together with
its parent. However it will continue using memory.
The OOM killer should be instructed to kill stopped processes in priority, not
sure how feasible that is though.
--
You received this bug notification because you are
22 matches
Mail list logo
