Hangouts tab is killed to free memory
Bug #1579817 reported by
Michael Hall
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Oxide |
Confirmed
|
Medium
|
Unassigned | ||
| webbrowser-app (Ubuntu) |
Confirmed
|
Medium
|
Unassigned | ||
Bug Description
The browser will kill non-focused tab processes when it needs to free up memory, which is usually fine, but when I have a hangout tab (or any video-conference, music streaming, etc) tab open I want to be able to navigate to other tabs without those being killed. Could tabs that are actively using the microphone, camera, or streaming either video or audio, be given an exception to the memory-killer, or at least given a different priority than static-content tabs?
Revision history for this message
| Olivier Tilloy (osomon) wrote | #1 |
| Changed in webbrowser-app (Ubuntu): | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
Revision history for this message
| Olivier Tilloy (osomon) wrote | #2 |
| Changed in oxide: | |
| status: | New → Confirmed |
| importance: | Undecided → Medium |
To post a comment you must log in.
This is a known shortcoming of the current implementation of the memory pressure handler in the browser. At the moment oxide doesn’t expose a score on webviews, nor does it provide a way to know whether a webview is playing video/audio/using webrtc, …
So the current mechanism is pretty dumb, all it does is pick the least recently viewed tab and unload it.
We will need a little help from oxide to write a smarter mechanism.