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

Issue 631982 link

Starred by 2 users

Issue metadata

Status: Duplicate
Merged: issue 622810
Owner:
Last visit > 30 days ago
Closed: Jul 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 1
Type: Bug



Sign in to add a comment

100% CPU usage in DevTools when inspecting Network tab error

Reported by ddascale...@gmail.com, Jul 27 2016

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.106 Safari/537.36

Steps to reproduce the problem:
1. Run this fiddle: https://jsfiddle.net/dandv/8cc5annk/
2. Open DevTools and go to the Network tab
3. Choose an image to upload to Google Cloud Vision. A 27-kb PNG file reproduced the issue (http://icons.iconarchive.com/icons/cornmanthe3rd/plex/512/Media-foobar-icon.png)
4. Click on the request in the Network tab that shows the 400 error

What is the expected behavior?
Details about that network request should be shown.

What went wrong?
Chrome CPU usage spikes to 100% for a core. Each reproduction of the behavior engages another core at 100%

Closing the offending tab doesn't reduce the CPU usage below 80% for the affected cores.

Did this work before? N/A 

Chrome version: 51.0.2704.106  Channel: n/a
OS Version: Ubuntu 16.04 64-bit
Flash Version: Shockwave Flash 22.0 r0

Uploading the same image at https://cloud.google.com/vision/ and inspecting the request doesn't trigger the bug, probably because the request didn't error out due to the invalid Google Cloud Vision key ('xxx' on line 1).
 
DevTools CPU 100% on network error.png
203 KB View Download
Components: Platform>DevTools>Network
Labels: -Pri-2 Pri-1
Owner: allada@chromium.org
Status: Assigned (was: Unconfirmed)

Comment 2 by allada@chromium.org, Jul 29 2016

Mergedinto: 622810
Status: Duplicate (was: Assigned)
This was caused by a patch that was fixed here:  http://crbug.com/622810  . The next stable release should resolve this.

Sign in to add a comment