Chrome Version: 58.0.3000.3 (Official Build) dev(32-bit)
OS: Android 7.1.1
What steps will reproduce the problem?
(1) Use multiple tabs in Chrome Dev on Android.
(2) Switch between apps.
(3) Switch back to Chrome.
What is the expected result?
Expect tabs to be responsive upon coming back to the Chrome activity.
What happens instead?
The renderer process hangs frequently. The tab switcher still works, although in some situations the "+" button to create new tabs is missing. Once a renderer is hung, nothing will bring it back. Closing and reopening Chrome Dev works around the problem.
I delayed filing this bug for a few days, so wouldn't be surprised if it's already been filed and fixed. I searched the bug database for open bugs matching"OS=Android hang" but the results were too noisy to tell.
Here's a link to a bug report captured while Chrome was still active and the foreground tab was hung. Sorry, accessible to Google employees only:
https://drive.google.com/open?id=0B5DES7PYkZBLYVNIZ2hOelhiOEl4RDFYcFBOc255RmRZYUpr
Hopefully it will contain a stack trace of the offending process.
Not sure who to CC: on this to get it triaged. Grace or Ted or John, could you help?
Comment 1 by jbudorick@chromium.org
, Feb 8 2017