Orphaned Developer Tools Process using 100% CPU
Reported by
richardk...@gmail.com,
Oct 20 2016
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.59 Safari/537.36 Steps to reproduce the problem: Don't know What is the expected behavior? Developer Tools should exit when its tab is closed. What went wrong? There is a Developer Tools process running, but the tab it was associated with has been closed. It uses 100% CPU and cannot be closed without exiting chrome. Did this work before? N/A Chrome version: 54.0.2840.59 Channel: stable OS Version: OS X 10.12.0 Flash Version: Shockwave Flash 23.0 r0
,
Oct 20 2016
I can't reproduce this on tip-of-tree. Could you please provide additional information? - can you reproduce this reliably? - does this also happen on a canary? - does this happen when inspecting a particular URL? - are there any other actions within the DevTools or page involved?
,
Oct 20 2016
- No, I only noticed it because of the sound of my fan so I have no idea exactly when or how it happened. - Not sure. - Hard to say, because it only happened once. - Don't know. Sorry that's not helpful at all. If this happens again, is there any way to get information about a DevTools process without having access to the tab it's connected to?
,
Oct 21 2016
Let's close this for now, since it's not actionable in its current form -- but please feel free to re-open if this happens again. Generally, you can troubleshoot devtools front-end by invoking devtools-on-devtools, but considering it's apparently in and endless loop, I'm not sure this will work -- so perhaps the only option would be attaching a native debugger. |
|||
►
Sign in to add a comment |
|||
Comment 1 by caseq@chromium.org
, Oct 20 2016