Thanks for the report!

By "freeze" or "frozen tab", what do you mean specifically?
"You can still click around, open the inspector, navigate" indicates that
Chrome is still active. I tried the page but have not yet seen freeze-ish
behavior.  Please help us finding the problem.

Other than you can click and navigate, what you *cannot* do? e.g. Can you
scroll, or see hover effect?

The web page is quite complicated and probably hard to minimize the
reproduction - so we would like to reproduce the case to see what is
the internal state.

Hi!

By Frozen, I mean that the rendering stops entirely. I can still click on links, which triggers a visit and is handled as expected(ajax loaded, history pushed and location bar updated), I can still scroll(and see the logs related to scrolling in the console). However, the page remains in the exact same state, ie no pixel change.
Resizing the window also doesn't adapt the content.
Some screenshots are white, which happened after switching to another tab and coming back to it.

Some screengrabs:
https://cl.ly/2I2T090V1B19
https://cl.ly/2C1s310S2O2z
https://cl.ly/0Q2F3q2H3T2q

I cannot reproduce systematically, but navigating the site seems to eventually trigger it(again, have seen on various computers).

I suspect(on no particular basis):
 - turbolinks, which does the ajax handling, and has a caching system(mostly used to handle ~history.back)
 - some DOM elements stored in memory between the pages, and it gets too much at some point, particularly in terms of rendering contexts(the /program page has many elements, each in their own z-plane)
 - the DOM element that is removed on page navigation has a z-index of 60px when it comes out. Could this be source of the error?

Once I get a frozen tab, what could i check to see if there is a problem?

Thanks for your input!

Thank you for providing more feedback. Adding requester "kochi@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Thanks for more info.

Blink has an event loop that handles events, animation, etc., and if it gets 
in a completely blocked state, even mouse event cannot happen - so in your case,
only the screen rendering (in Blink's terminology it may be "painting") stopped
and event loop seems working.

I watched the videos, but haven't got any clue on why it stopped rendering.
(seeing lots of errors/warnings on the console, but it is not an issue?)

~5 minutes of navigation didn't get a repro.
(I tried on Macbook Pro FYI, as "I've seen this behavior happen on various
computers, although only Mac OS X." in the original comment.)
As we haven't reproduced the problem locally, we have little to make progress
on this - except for spending more time on playing around the page to hope
it reproduces.

If you could minimize the problem (minimal set of HTML, JS and CSS)- it would
be most helpful. But if the size (e.g. number of elements used in the page)
matters to reproduce the issue, minimizing would be very hard.

Anyway, without reproduction it's too hard to identify the issue :-(

Feedback timeout