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...
Comment 1 by w...@chromium.org
, Nov 9