Browser gets killed before renderer |
||
Issue descriptionBrowser and foreground renderer are both at prev bucket after Chrome goes to background, but it seems like the browser may be getting killed first by Android. Figure out on which systems that's the case and explore potential solutions. One potential solution is to listen to memory pressure signals in background and unbind/waive the renderer binding in order to ensure the browser doesn't get killed first.
,
Jan 11
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||
►
Sign in to add a comment |
||
Comment 1 by haraken@chromium.org
, Jan 10 2018