In M50, there was a 10x spike in ConOps reports for WaitOrKill - basically hung renderers.
https://bugs.chromium.org/p/chromium/issues/detail?id=609262#c83
Having looked at a plethora of metrics, including
* CrashExitCodes.Renderer: RESULT_CODE_HUNG
* Uploaded crashes with [Renderer hang] in the signature.
* Specific crashes such as [Renderer hang] content::RendererWebCookieJarImpl::cookies, which spiked in M50 stable.
We don't see any early warning signs in Canary, Dev, or Beta that Chrome is hanging 10x as frequently as before. I suspect this is because Canary/Dev/Beta users are much more willing to cmd+W a tab that looks like it might be hung.
I heard that siggi@ is looking into Hung renderers in general, so cc-ing him to see if he has any ideas.
Comment 1 by wfh@chromium.org
, May 20 2016