Chrome DevTools 100% CPU

T

7

20

I have Google Chrome Version 31.0.1650.57 on Lubuntu 13.04, and since a couple of weeks, suddenly the dev tools eats up all the CPU to 100% even doing nothing..
I mean really nothing, like
open chrome with a default tab
open dev tools -> CPU 100%
close dev tools -> CPU 1%
Do someone know something that could help understanding?

Taste answered 28/11, 2013 at 23:18 Comment(0)

T

36

Strange, i've been struggling for days, and i found the solution right after asking here..
some days ago looking inside DevTools Settings -> Workspace i set a local folder.
now i have unset it and the CPU issue vanished!
good!
but can someone explain me what happened?

Taste answered 28/11, 2013 at 23:34 Comment(2)

Take a look at this: developers.google.com/chrome-developer-tools/docs/… This feature does look pretty cool actually (even if it doesn't look like it's very well implemented). – Crazy 29/11, 2013 at 0:33

Unfortunately this did not work for me. I removed workspace mapping to local folder but as soon as I hit a break point the CPU utilization goes to 100%. – Carter 2/6, 2015 at 17:55

C

4

I had the same problem (100% cpu utilization when I hit a break point) and disabling the Chrome Workspace mapping did not resolve my issues.

I tested it in Firefox and found the same behavior.

I think the problem is caused by Flash plugin. I disabled flash plugin in Chrome and it stopped the problem. But caused another one which prevents me from actually hitting any breakpoints.

Carter answered 2/6, 2015 at 18:55 Comment(0)

A

2

In my case I have a MacPro 15in and recently I started to have those issues only when opening the DevTools, it was taking about one min for the console to respond, I tried the Workspace folder solution and it partially worked but the console was still frozen for a few seconds.

I disabled the Hardware acceleration: Settings -> Advanced -> System -> Use hardware acceleration when available and that did the trick.

Note: is still frozen for about 2-5s but is a big change from the original min I started.

Ahmad answered 24/3, 2020 at 17:30 Comment(1)

Same on a windows machine. Running multiple dev servers on localhost on one project/page. Console was nearly unusable. After disabled hardware acceleration I am now able to use chrome. – Pilcomayo 29/4, 2020 at 8:50

L

1

Today/yesterday I had the same issue, everytime I opened devtools my CPU was pinned closed to 100%. After reading some of the answers here I remembered yesterday I had set a local Override for a network request. I removed the override & all other override related cofiguration and the issue was gone. Happy days.

Lilith answered 19/4 at 9:49 Comment(0)

I

0

It was driving me crazy. Every time I opened the tab Developer Tools was using 100% CPU and it was impossible to close unless I end the process with the task manager.

In my case I made it work restoring the default settings at Settings->Advanced->Reset settings

Ianiana answered 15/8, 2020 at 15:7 Comment(0)

F

0

I had an extension called Stylish after I disabled it, it got fixed

Fireball answered 21/7, 2022 at 13:34 Comment(0)

C

0

In chrome dev tools settings under preferences tab, I clicked "restore defaults and reload", and the high cpu disappeared. For me the CPU was only like 6%, but regardless, dev tools should never need that much CPU, and it was kicking up my fans regardless, so quite obnoxious

Cerebrospinal answered 22/1 at 16:7 Comment(0)

Recommended topics

Hot tags