- killing the whole cgroup would be a valid solution for webapps per-se since atm they are mostly single webview entities but most likely not for the webbrowser-app which basically is the host for multiple webviews. Killing the whole webview bits might be trickier and not desirable from the perspective of per-tab state preservation ...
- there are some tasks in the pipe that would deal with those issues (discussed during the Washington sprint):
- making webapps a single process (which would simplify the klling process),
- having an api for the webview to be informed that the renderer process has been killed (ongoing work and also needed to properly solve other issues, like proper handling of window.close()),
- clever handling of background tabs strategies for the oom killer ...
Those above are being prioritized and/or worked on atm,
To be noted:
- killing the whole cgroup would be a valid solution for webapps per-se since atm they are mostly single webview entities but most likely not for the webbrowser-app which basically is the host for multiple webviews. Killing the whole webview bits might be trickier and not desirable from the perspective of per-tab state preservation ...
- there are some tasks in the pipe that would deal with those issues (discussed during the Washington sprint):
- making webapps a single process (which would simplify the klling process),
- having an api for the webview to be informed that the renderer process has been killed (ongoing work and also needed to properly solve other issues, like proper handling of window.close()),
- clever handling of background tabs strategies for the oom killer ...
Those above are being prioritized and/or worked on atm,