New issue
Advanced search Search tips

Issue 657003 link

Starred by 1 user
Status: WontFix
Owner:
kozy@chromium.org
Closed: Dec 2017
Cc:
dgozman@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 3
Type: Bug



Sign in to add a comment

Setting break point stalls dev tools with 100% CPU usage

Project Member Reported by malteubl@google.com, Oct 18 2016 
Version: M54, also reproed in M53 at least
OS: OS X

What steps will reproduce the problem?
(1) Clone https://github.com/ampproject/amphtml
(2) Install local dev env https://github.com/ampproject/amphtml/blob/master/DEVELOPING.md#installation
(3) Run `gulp test -w`
(4) Wait for Chrome to start
(5) Open random JS file and set break points

What is the expected output?

Dev Tools should work as expected

What do you see instead?

Dev Tools use 100% CPU and become unresponsive until restarting them.


Please use labels and text to provide additional information.

Comment 1 by malteubl@google.com, Oct 18 2016 

This is most likely related to source maps. When it works, the view some times jumps into unmapped view.

Comment 2 by caseq@chromium.org, Oct 18 2016

Cc: dgozman@chromium.org
Owner: kozyatinskiy@chromium.org
Status: Assigned (was: Untriaged)

Comment 3 by kozyatinskiy@chromium.org, Dec 2 2016

Labels: Hotlist-Polish

Comment 4 by kozyatinskiy@chromium.org, Oct 16 2017

Owner: kozy@chromium.org

Comment 5 by kozy@chromium.org, Dec 12 2017

Status: WontFix (was: Assigned)
Thanks for your report, I believe that since 2016 we fixed and speed up a lot of related parts including source map processing and setting breakpoints. If it still an issue feel free to reopen this bug.
►

Sign in to add a comment