Google Chrome developer tools works very slow

Question

Sinсe Google Chrome was updated to 50.x version, it become impossible to work with DevTools. This issue reproduced mostly in \"Network\" tab. Every time when you click on \"requ

Answer 1

I'm using the Version 61.0.3163.79 and I have the same issue that this post talks about.

With some searches I found out that the problem was in the user that I was using. What I tried was to enter int google chrome as guest and the devtools became faster again.

So what I did was:

1. Check out if debugging using the guest user is faster as it should be.
2. Logout from the account.
3. Clean all cache associated to google chrome.
4. Restart the PC (but i think closing the browser is enough)
5. Login again in your account.

I hope this could help other people with same problem.

[EDIT:]

I found out that after some time (weeks) the google chrome dev tools will get slower again. So I tried the following solution and it worked:

1. Open the dev tools
2. Go to the Sources tab.
3. Cleaned all watched variables, breakpoints, DOM breakpoint and Event Listeners breakpoint.

[SECOND EDIT:]

After some weeks, the issue came again. What I did was installing the google canary Version 64.0.3249.2 canary (64-bit) and my problems vanished.

For who's that doesn't know what is canary, please check this link.

Answer 2

Google is aware of the problem - https://bugs.chromium.org/p/chromium/issues/detail?id=624097

The problem seems to have vanished in v.53 - they are currently trying to figure out what fixed it. If possible, the fix will be merged back to v.52. But at least they are working on it.

Answer 3

Finally, a solution has been found which helped me after such a long time and after so many failed attempts to fix it: Solution on Google Chrome Forums

Go to chrome://flags/#force-color-profile

Change it to sRGB

Since Google does not allow direct links to chrome:// you'll have to insert the colon by yourself, or enter the whole link manually into your toolbar.

Answer 4

I also face same issue.

I tried unchecked toggle screencast. Now it is working fine.

Answer 5

Make devtools snappy again by deactivating all breakpoints:

Go to the Sources tab, show the debugger (may be hidden) and hit Deactivate breakpoints.

(Chrome v62.0 on Windows 10)

Answer 6

Reduce size of resource being overridden

Only overriding files with less lines of code worked well for me. I landed here because I was overriding a file which had 35,000 + lines of Javascript.

Further, if your resource is a new one - i.e. it is not included in a script tag or link tag, you can override main html document and add the tag : <script src="/my-new-script.js"></script>. Add the file to your domain-root within the Overrides folder on Chrome:

overriding HTML

then overriding CUSTOM SCRIPT:

Good Luck...