touch-packages team mailing list archive
-
touch-packages team
-
Mailing list archive
-
Message #30735
[Bug 1388089] Re: [webapp-container] apps are not handled by lifecycle management properly
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,
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu.
https://bugs.launchpad.net/bugs/1388089
Title:
[webapp-container] apps are not handled by lifecycle management
properly
Status in Oxide Webview:
New
Status in Web Browser App:
New
Status in “qtmir” package in Ubuntu:
New
Status in “webbrowser-app” package in Ubuntu:
New
Status in “qtmir” package in Ubuntu RTM:
New
Status in “webbrowser-app” package in Ubuntu RTM:
New
Bug description:
in image 137, if you open a gazillion of apps and have webapps among
them, the webapp screenshots never turn blurry when the OOM score is
reached on high memory pressure ... once you switch to such a webapp,
the whole content window turns white (sometimes the app header stays
around, sometimes the whole app window is white).
seemingly the renderer is lifecycle managed and gets properly OOM
killed on high memory pressure , but the frontend of the webapp does
not.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oxide/+bug/1388089/+subscriptions
References