Could you try with a new profile? (or run as --user-data-dir=some_folder

I just tried, no improvements on the elements panels, it's still very sluggish (I tried on a google search results page, "test")

Unable to reproduce the issue on windows 7 using chrome version 53.0.2774.3.Not observed any difference while opening elements,source tabs and typing in console.
Please find the attached screen cast and confirm anything missed here.

Request you once please try the issue on latest version with new profile if the issue still persists please provide us any screen shot for better understanding the issue.

Thank you!

Deleted: 621532.mp4 1.1 MB

	621532.mp4 1.1 MB View Download

Hello, sorry for the late reply, the process to get files out from here is very slow. I made a screen cast to show what happens:

Deleted: slow.mp4 716 KB

	slow.mp4 716 KB View Download

Deleted: chrome=version.txt 1.7 KB

chrome=version.txt 1.7 KB View Download

Thank you for providing more feedback. Adding requester "kavvaru@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Can you capture a trace while you reproduce the slowness?
https://www.chromium.org/developers/how-tos/submitting-a-performance-bug

Here is the trace.

What I'm doing here first is console keystrokes (hold key pressed) with Elements open first,

Then I switch to "console" only pane and repeat the same process.

Deleted: trace_awesome-trace.json.gz 4.8 MB

trace_awesome-trace.json.gz 4.8 MB Download

#632372 may be relevant here

https://bugs.chromium.org/p/chromium/issues/detail?id=632372&q=snippets&colspec=ID%20Pri%20M%20Stars%20ReleaseBlock%20Component%20Status%20Owner%20Summary%20OS%20Modified

Same here, 53.0.2785.57 beta-m (64-bit). I can barely use devtools now. Trying to even scroll in the Elements or Sources tab takes 500+ ms to respond and scrolling is barely 1-2 fps with high CPU usage.

Attached trace.

Deleted: trace_Tue_Aug_16_2016_12.07.02_AM.json.gz 4.1 MB

trace_Tue_Aug_16_2016_12.07.02_AM.json.gz 4.1 MB Download

This is accessibility support enabled that is slowing your devtools down. If you do not need it, go to chrome://accessibility/ and turn "Global accessibility mode" to "off".

We are looking into fixing it.

Huzzah! That fixed it, thanks.

It seems "Global accessibility mode" resets to "on" every time the browser is opened.

You may have an app installed that is forcing it on. On android it happens with password managers often.
It could be a password manager, antivirus, or some other app that wants to read the content of every page you visit.

It likely has escalated privileges, though. On Mac you need to give apps like this permission in Prefs / Security/ Accessibility.  Good luck

Thanks for the info, must be LastPass. I've jumped back up to stable until it's cleared up... gotta love separate release channels :)

Thanks, turning Global accessibility mode on chrome 52 does solves the problem on my station. However, I have to flip in off every 10 minutes or so as it switched back again to on every time.

This issue is still alive and well on 54.0.2840.99 m (64-bit) - Win10. Dev tools performance tanks if global accessibility mode is turned on. If I turn it off to fix it, extensions like LastPass constantly turn it back on.

Is that how it's going to be? Find and disable all extensions that turn on global accessibility mode if I want to use dev tools? Back in August you said this was known issue and were looking into a fix. Any news?

#19 - I am not sure an extension is capable of turning on global accessibility mode. If it does that, it might be a bug. Can you search for an issue or file an issue for it and comment here with its ID? Thank you.

#19 - also, if you follow https://bugs.chromium.org/p/chromium/issues/detail?id=624097#c32 - that would help narrow down the issue and fix it quicker.

Cleaning up "Needs-Review" label as we are not using this label for triage anymore. Ref bug for this cleanup 684919

Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot