Task manager does not reflect renderers kept alive by service workers. |
|||||
Issue descriptionmacOS, ToT [d1054682ea0b2d1ff303f10a06a5eea374a2b532] Repro steps: 1) Launch chrome with a clean profile. [ntp is loaded] 2) Close the window [thus, theoretically, destroying the renderer] Observe: The renderer is no longer present in the task manager list, but the process is still present. This is because the process is kept alive by a service worker.
,
Nov 15 2017
+ avi, actually this time. Hm, it looks like if we cannot fast kill the renderer process, then the RPH is destroyed [causing a NOTIFICATION_RENDERER_PROCESS_TERMINATED notification.], and nothing is around to listen for the process death and send the NOTIFICATION_RENDERER_PROCESS_CLOSED notification.
,
Nov 16 2017
There is also ongoing work to show service workers themselves in the task manager: issue 716609. Would fixing issue 716609 solve this automatically, or do we have an additional bug with the notification type?
,
Nov 16 2017
The fact that NOTIFICATION_RENDERER_PROCESS_CLOSED isn't sent all the time seems more like a bug of the implementation of RPH itself [or at least the documentation could use some revising]. I don't believe there's any problem specific to service workers.
,
Nov 16 2017
nick@ Please feel free to merge this issue to the issue 716609.
,
Sep 26
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by erikc...@chromium.org
, Nov 15 2017