Google Chrome Developer Toolkit is Slow

google-chrome javascript-debugger
Matt Cashatt picture Matt Cashatt · Nov 14, 2011 · Viewed 15k times · Source

I have been using Google Chrome's dev tool kit (element inspection, stack trace, javascript debugging, etc.) for some time with great success.

However, about two weeks ago, it suddenly became VERY sluggish. For example, when I right-click an element in the UI and then click "Inspect Element", or when I simply press F12, the code window takes 30-45 seconds to come up. It used to happen in less than a second.

Has anyone else run into this problem? If so, were you able to correct it? How?

Thanks in advance!

Matt

Answer

Pablo Montilla picture Pablo Montilla · Mar 10, 2014

I've had the same problem, tried the same solutions without luck, until I fired procmon and saw that Chrome was actually reading my entire Projects folder (which is several hundred thousand files worth).

There was a reference to that folder in the Workspace/Folders section in the dev tools Settings app. Removing the reference solved the problem.

Related questions

How can I inspect element in chrome when right click is disabled?

I want to debug a info box that shows when I mouse over a google map marker. But google map disables right click anywhere on the map canvas, so I can't inspect the element for debugging / viewing purposes. I tried …

Read More
How exactly does document.cookie work?

If I get Chrome to show me document.cookie by going into the console and typing document.cookie; it'll give me, say: "name=John; gender=male"; But then if I type in, say, document.cookie = 5; all it does is add 5; …

Read More
Running code snippets from Google Chrome console command line, using (experimental) code snippets feature?

Reference: Using the new code snippets feature in google chrome I am using the code snippets in google chrome, so say I have a snippet file. check_consistency.js Is there an api or a global object through which we …

Read More