New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 903961 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Tabs keep "hanging" with the loaded spinning and the tab unresponsive

Project Member Reported by w...@chromium.org, Nov 9

Issue description

Chrome Version: 72.0.3593.0
OS: ChromeOS Fizz

What steps will reproduce the problem?
Not sure what triggers this, but I'm currently seeing it with a JIRA bug page.

What is the expected result?

Expect that the page loads content, and continues to load any on-demand content until the spinner stops.

What happens instead?

Page loads some initial content, but then becomes completely unresponsive - page will not scroll, and if resized then it becomes blank.  Spinner continues indefinitely, seemingly without any "hung renderer" timeout kicking in, which is surprising.

Although the renderer appears to be "hung", it continuously consumes 2% of a CPU core, indicating that it's a live-lock. The low CPU usage suggests an IPC ping/pong live-lock, or wait-with-timeout-and-retry loop.  Will try to get a crash dump...
 
Asking to "inspect" the renderer and to profile it unsurprisingly hangs DevTools at "Initializing profiler..."
Cc: creis@chromium.org nasko@chromium.org
Components: -Internals Internals>Sandbox>SiteIsolation
Some experiments:

1. Navigating to JIRA dashboard works fine.
2. Re-opening the bug page (by clicking on a link from GMail) with Dashboard visible still hangs the bug page, but not JIRA (separate processes).
3. Duplicating the hung bug page tab tries to load the duplicate in the same renderer as the original, so that is also hung.
4. Copying the hung bug page to a new tab, it loads fine.

Tentatively tagging SiteIsolation, since it seems that this is specific to opening a tab via a link from a GMail tab, versus loading a URL in a new tab.

Sign in to add a comment