New issue
Advanced search Search tips

Issue 646889 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 644450
Owner: ----
Closed: Sep 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Tab freezes on click in specific conditions

Reported by yannick....@caldera.com, Sep 14 2016

Issue description

Chrome Version       : 53.0.2785.113
URLs see below
Other browsers tested:
     Safari: OK 9.1.1
     Firefox: OK 47.0.1

What steps will reproduce the problem?
(1) Open the page in Chrome for Mac
(2) Click a button

What is the expected result?

Some javascript runs and elements are added to the page.


What happens instead?

The tab freezes.



The website this happens on is private, but I can share access to it with someone privately if needed. the problem is 100% reproducable.

I have a button on a page; when I click that button, it triggers a bit of javascript that adds some elements to the page and fires off network requests. However, as of version 53 of Chrome, the tab freezes instead (if I downgrade to v52 for example, everything is ok).

This page is in an iframe; if I open the page in a separate tab, it works.

The devtools are still responsive but not actually working. I can't get a timeline to inspect memory usage or anything. The freeze is immediate, there's really nothing happening AFAIK.

i'm happy to do more digging but I don't know how to get anything interesting out of the crash report.
 
I tried to narrow things down a bit and managed to send a crash report

Crash ID: crash/c1602df500000000

The crash happens when a DOM with overflow auto is added to the DOM. So this issue might b a duplicate of https://bugs.chromium.org/p/chromium/issues/detail?id=644450 or https://bugs.chromium.org/p/chromium/issues/detail?id=644635 (probably the first as I also use flex layout, but not table).

The problem is still present in 55.0.2861.0 canary (64-bit)
Cc: szager@chromium.org
Components: Blink>Layout

Comment 3 by szager@chromium.org, Sep 15 2016

Unfortunately, that crash report won't help debug a hung renderer.  I suspect you're right that this has the same root cause as  issue #644450 , but it's impossible to say for certain without a reproduction.

Comment 4 by e...@chromium.org, Sep 17 2016

Mergedinto: 644450
Status: Duplicate (was: Unconfirmed)

Sign in to add a comment