Comment 5 for bug 1443019

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 an extended
period of time(10 - 50 minutes). After some time, the page becomes white.
After a restart, I can browse again for about the same period, and then
again white. I don't think it is caused by the individual page. Maybe a
memory leak? What can I do to diagnose this issue?

2015-04-15 11:19 GMT+02:00 Olivier Tilloy <email address hidden>:

> 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 notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1443019
>
> Title:
> renderer process is killed on image-heavy pages on krillin
>
> Status in Oxide Webview:
> New
> Status in Web Browser App:
> Confirmed
> Status in webbrowser-app package in Ubuntu:
> Confirmed
>
> Bug description:
> On the BQ ubuntu phone, while browsing image-heavy pages, the browser
> suddenly turns completely white and unresponsive. Closing the app and
> restarting it fixes the problem.
>
> example: I can't watch this page to the end, because the browser
> crashes in the middle... https://imgur.com/gallery/NnGyq
>
> I have this on a lot of websites, after browsing for 30 minutes, the
> browser crashes...
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/oxide/+bug/1443019/+subscriptions
>