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

Issue 673958 link

Starred by 0 users
Status: WontFix
Owner: ----
Closed: Jan 2017
Cc:
█ brajkumar@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Chrome Dev Tools Crashes on Page Load

Reported by michael....@gmail.com, Dec 14 2016 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.99 Safari/537.36

Steps to reproduce the problem:
1. Open Dev tools (by pressing F12)
2. Go to the following site: https://roa.sdcourt.ca.gov/roa/
3. While viewing the webpage, use the keyboard shortcut Ctrl+Shift+C to open the inspector.

What is the expected behavior?

What went wrong?
It crashes.

Crashed report ID: 

How much crashed? Just one tab

Is it a problem with a plugin? N/A 

Did this work before? N/A 

Chrome version: 54.0.2840.99  Channel: n/a
OS Version: 10.0
Flash Version: Shockwave Flash 24.0 r0
chrome dev crash.png
185 KB View Download

Comment 1 by nyerramilli@chromium.org, Dec 14 2016

Components: Platform>DevTools
Labels: Needs-Milestone
Adding 'Needs-Milestone' label, TE will check the issue and update the bug with comments & tag with respective Mstone

Comment 2 by brajkumar@chromium.org, Dec 14 2016

Cc: brajkumar@chromium.org
Labels: Needs-Feedback
Unable to reproduce the issue on Windows-10 using chrome latest stable M55-55.0.2883.87 by following steps mentioned in the original comment. Observed no crashes on pressing Ctrl+Shift+C in dev tools.

michael@ - Could you please upgrade your chrome to latest stable #55.0.2883.87 and recheck for this issue. If issue still persists please provide sample crash ID's from chrome://crashes for further assistance.

Thanks!

Comment 3 by michael....@gmail.com, Dec 14 2016 

Here is the crash id for my version of chrome: 583eb188-ebf5-4ba8-81c7-a5d6bd9b1430

Comment 4 by chenwilliam@chromium.org, Dec 16 2016 

The crash ID should look like: "8a01000500000000"
ex: Crash ID Chrome (Server ID: 8a01000500000000)

Could you include the crash ID? Thanks.
Project Member

Comment 5 by sheriffbot@chromium.org, Dec 26 2016

Labels: -Needs-Feedback Needs-Review
Owner: brajkumar@chromium.org
Thank you for providing more feedback. Adding requester "brajkumar@chromium.org" for another review and adding "Needs-Review" label for tracking.

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

Comment 6 by michael....@gmail.com, Dec 26 2016 

Ah, here it is: 049863e300000000

Comment 7 by woxxom@gmail.com, Dec 26 2016 

michael@, try disabling all AdBlockPlus extensions (your screenshot contains one in devtools).

Comment 8 by michael....@gmail.com, Dec 28 2016 

At the time, this was easily reproducible, but I can't reproduce it anymore, with or without AdBlock plus enabled. In the developer tools I see the following message "Uncaught RangeError: Maximum call stack size exceeded", so perhaps this has something to do with it. 

Unless you have other suggestions, perhaps this should be closed as cannot reproduce. I'll request to reopen if I see it again.

Comment 9 by jmukthavaram@chromium.org, Jan 4 2017

Labels: -Needs-Review
Status: WontFix (was: Unconfirmed)
As per Comment#8, marking this issue as Wontfix.

Please feel to free to log a new defect once you face the issue again.

Thank you.

Comment 10 by jmukthavaram@chromium.org, Jan 4 2017

Owner: ----
►

Sign in to add a comment