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

Issue 627415 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Last visit 29 days ago
Closed: Jul 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

DevTools sometimes hang when after a specific page is loaded

Reported by m.go...@gmail.com, Jul 12 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.106 Safari/537.36

Steps to reproduce the problem:
1. Load a problematic page
2. Open DevTools
or:
1. Open a new tab
2. Open DevTools
3. Open a problematic page

What is the expected behavior?
DevTools should load & work properly.

What went wrong?
DevTools take 200% CPU and they're frozen. They don't reply to user input. If I open DevTools *after* loading the problematic page, the Elements tab freezes in an empty state. If I open the DevTools first, I see head & body tags displayed and frozen in the middle of flashing their tagnames (which means they're being modified).

Did this work before? Yes In 54.0.2793.0

Chrome version: 54.0.2794.0  Channel: canary
OS Version: OS X 10.11.5
Flash Version: Shockwave Flash 22.0 r0

I could only reproduce it locally on a dev version of one page with a custom self-signed certificate if that matters. The public version of this page works fine.
 

Comment 1 by alph@chromium.org, Jul 12 2016

Cc: alph@chromium.org
Owner: lushnikov@chromium.org
Status: Assigned (was: Unconfirmed)
It's hard to tell whats going having just a description.
Could you please help to debug it?

Once you reproduce the behavior on e.g. Elements panel,
open DevTools on DevTools (just press Cmd+Opt+I having Elements panel focused).
In the newly opened DevTools check the Console tab has no error messages and record a Timeline for several seconds.
Then please save the recording and attach it to the bug report. Thanks.

Labels: Needs-Feedback
Can you reproduce this on Chrome Canary?

There was a regression in rendering engine which caused such a behavior, e.g.  issue 622810 . It should be fixed in Canary.

Comment 3 by m.go...@gmail.com, Jul 14 2016

> Can you reproduce this on Chrome Canary?

Considering that I'm reporting a bug in Canary... :) Also, the info about that is included in the report:
"Chrome version: 54.0.2794.0  Channel: canary"

> Once you reproduce the behavior on e.g. Elements panel,
> open DevTools on DevTools (just press Cmd+Opt+I having Elements panel focused).

That doesn't work; pressing Cmd+Opt+I when the Elements panel is focused just closes the DevTools.

Comment 4 by m.go...@gmail.com, Jul 14 2016

I found a public site that triggers the same error: http://www.gazeta.pl/. Follow the steps:

1. Open a new tab.
2. Open DevTools on this tab.
3. Enter "gazeta.pl" in the address bar & see the freeze.
Cc: allada@chromium.org
Status: Fixed (was: Assigned)
Thanks

The offending commit was reverted: https://codereview.chromium.org/2151943002/
The revert should hit the Canary soon.

Comment 6 by m.go...@gmail.com, Jul 15 2016

Thanks for the fix!

BTW, I've noticed only now that I couldn't open DevTools on DevTools because first the DevTools to be inspected has to be detached from the main window... After doing that, it works. Please remember to include this info if you ask others to follow these steps in the future.

Sign in to add a comment