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.
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.