** Changed in: avila
Assignee: Chunsang Jeong (chunsang) => (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/1542002
Title:
[browser] opening
** Changed in: webapps-sprint
Milestone: sprint-22 => sprint-23
--
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/1542002
Title:
[browser] opening multiple tabs
That’s most likely because the behaviour of the mechanism to unload
background tabs when running low on memory has recently been tweaked
(see bug #1576639).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in
Couldn't reproduce it with recent frieza image even with opening 10 tabs
from browser. Mem usage decreased quickly when there wasn't activity and
device didn't get slow when swiping.
current build number: 106
device name: frieza
channel: ubuntu-touch/rc-proposed/bq-aquaris-pd.en
last update:
** No longer affects: canonical-devices-system-image
--
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/1542002
Title:
[browser] opening multiple tabs causing major
** Also affects: webapps-sprint
Importance: Undecided
Status: New
** Changed in: webapps-sprint
Assignee: (unassigned) => Olivier Tilloy (osomon)
** No longer affects: webapps-sprint
** Also affects: webapps-sprint
Importance: Undecided
Status: New
** Changed in:
Not sure there’s anything left to investigate on that one (aside from
tuning the OOM killer to favour killing renderer processes over the
browser process).
** Changed in: webbrowser-app (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member
I did an experiment: I commented out the code that unloads background
tabs in the browser, and opened a large number of tabs with memory-
hungry websites (google maps, here maps, google docs, youtube, google
plus, …).
The OOM killer eventually kicked in, but it didn’t kill oxide renderer
The reason why the OOM killer never kicks in is because of recent
changes in the browser (https://bazaar.launchpad.net/~phablet-team
/webbrowser-app/trunk/revision/1361, released with version
0.23+16.04.20160223-0ubuntu1) which automatically unload background tabs
when it thinks the system is
I've assigned it to chunsang, but his queue is quite long.
** Changed in: canonical-devices-system-image
Assignee: John McAleely (john.mcaleely) => David Barth (dbarth)
** Changed in: avila
Assignee: (unassigned) => John McAleely (john.mcaleely)
** Changed in: avila
Assignee:
10 matches
Mail list logo
