Renderer often OOM-killed, need to reload the current page

[Michał Sawicz]

It often happens to me, especially when browsing websites heavy i images, that the renderer gets killed and I need to reload the page. It was even worse when the address bar was hiding as that resulted in the browser being unusable at all.

[Olivier Tilloy (osomon)]

I sometimes see that too. Not sure how to address it though. Eventually, if the system runs out of memory, it will kill processes to free up some memory, and renderer processes are often good candidates.

However we could probably display a user-friendly message when that happens. This depends on bug #1375272.

[Michał Sawicz (saviq)]

I think the problem is that the renderer uses too much mem, all the background apps have already been killed, it's only the current page left... and that gets killed, too...

[Olivier Tilloy (osomon)]

Added an oxide task, we’ll need to look into memory usage.

Michał, could you grab a snapshot of how much memory the renderer processes use on your device when browsing heavy pages? That would help assessing if oxide is doing something wrong.