related: https://bugs.launchpad.net/ubuntu/+source/webbrowser-
app/+bug/1375272
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1443019
Title:
renderer process is killed on image-heavy pages on
** Also affects: webbrowser-app (Ubuntu RTM)
Importance: Undecided
Status: New
** Changed in: webbrowser-app (Ubuntu RTM)
Status: New = Confirmed
** No longer affects: webbrowser-app
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I can reproduce the issue: I’m browsing to
http://m.imgur.com/gallery/BBjgJW3, then swiping right-to-left to browse
through images in the collection (a good number of them are animated
GIFs, if that matters), and observing top’s output while doing that. The
memory used by the renderer process
This happened after browsing imgur for 10 minutes:
May 3 07:54:22 ubuntu-phablet kernel: [90155.559088]type=1400
audit(1430632462.017:437): apparmor=DENIED operation=open
profile=com.ubuntu.developer.webapps.webapp-gmail_webapp-gmail_1.0.25//oxide_helper
So when the page becomes blank, that means that the system killed the
renderer process because it considered that it was using too much
memory. When that happens, could you grep for 'oxide-renderer' in
/var/log/syslog, and paste the relevant section (see comment #1 in this
report for how it looks
Just tested on a nexus 10 (that’s the only working android device I have
at hand right now), and the renderer is never killed, but it seems its
available memory is capped (either by chromium itself or by android), so
after a while it stops loading images, silently.
--
You received this bug
I don’t know what other mobile browsers do, there may be a way to tell
the renderer to free up the memory used by areas of the page that are
far out of view. Adding an oxide task to investigate this possibility.
** Also affects: oxide
Importance: Undecided
Status: New
--
You received
Thank you for your help!
I have a feeling there are two issues here.
One issue is the case of a page that has clearly too much pictures.
Freeing memory of stuff far outside of view might and showing an error
message be a good solution.
However, I have the same issue after regular browsing for
