Chrome v50 network inspector really slow - google-chrome

today my chrome is gone to v50 and I noticed a dramatic slowing when trying to open request/response headers detail in the devtools.
Am I the only one?

I am having the exact same problem after I upgrade to build 50.0.2661.xxx, and I don't use any theme. For now I just have to downgrade it to build 49.0.2623.xxx.

Google Chrome v51 fix this issue
Edit. It seems not

The bug report is available here on the chromium tracker.
According to the comment, the issue is fixed for v52.

I have been having the same issue over the last week. Finally figured out it was a dark theme extension I was using for my dev tools. (DevTools Theme: Zero Dark Matrix) Removing it fixed the issue.

I also noticed the same behaviour in v50. Updating to V51 fixes the issue.

Related

Dev Tools auto-complete doesn't work on chrome 35, ubuntu 14.04

After update to chrome 35, autocomplete in dev tools doesn't work. Is it only my issue?
Checked windows and mac, all works..
I've got some similar problems, but just on Styles panel on Elements tab. Here, I've opened an issue just to this case:
https://code.google.com/p/chromium/issues/detail?id=376763&thanks=376763&ts=1400852713
I know it's not a solution, but it's the best we can do. We have to wait for someone at google (or that's involved with chromium project) fix it, and then release a new version patching it.
An alternative is using Chromium from ubuntu Software Center for now (it's still at version 34, so the autocomplete works): https://apps.ubuntu.com/cat/applications/chromium-browser/
UPDATE
This bug has been fixed on version 36
The issue has been fixed in the beta version.
(works in the current version: 36.0.1985.49 beta)
Can be download from http://www.google.com/intl/en/chrome/browser/beta.html
edit:
Considering the initial message, I assumed the problem was to pop the autocomplete box in the source files search as i enter in this issue. If the problem ain't relative to this, sorry.
In the last version the auto-completion menu in dev tools doesn't appears automatically anymore, u need to press cmd+P or cmd+O (mac) to open it.
I've got the same problem. It's really annoying.
Besides, on the Elements tab, when you double click the attribute of an arbitrary tag, the attribute is automatically emptied, which, i think, is not really expected.
Hope these issues get solved as quickly as possible.

html title attribute not showing as tooltip in Chrome

Recently updated my Google Chrome to version 32.0.1700.76 m and it looks like tooltips have stopped appearing over html elements with the 'title' attribute set.
<span alt="Testing" title="Testing">hhh</span>
Here is an example jsFiddle:
http://jsfiddle.net/ricksuggs/cDhEL/
I thought it was an HTML standard, it is still working in Firefox, anyone else experiencing the issue?
Version 32.0.1700.76 m works fine for me. Have you tried just clearing your Chrome browser cache to make sure it's not a caching issue?
Unfortunately, this is an old bug that have pop with version 32.0.1700 and is still present in v55 on some system such as mine too.
If you encounter this bug. Please go to http://download1.srware.net/old/iron/win/portable to test version 31 then 32. If you find out it works with v31 but it doesn't with v32, please report it in the chromium bug tracker issue. Specify your setup sharing a link provided by DriversCloud.com to help dev to fix it. They need feedback and details.

Tabs In Google Chrome Have gotten clobbered, How to reset?

For some reason, my tabs have gotten crunched on my google chrome browser (see picture attached). I've try to go into settings and reset browser but it does not change. I'm running windows 8.1 with my fonts at 150% because I have big monitors.
Version 31.0.1650.63 m
I just did some more searching and found the answer (though it makes the screen pretty ugly, google does not do a good job with this)
http://productforums.google.com/forum/#!topic/chrome/BnI6QInBHC4
"I found the answer posted by Azmeer Kahn on November 22. Type chrome://flags in the address and scroll WAY down to the HiDPI section - change from default to Enable. Whew. Worked for me."
Are these tabs pinned? I had similar problems with pinned tabs in early versions of chrome. Unpinning and pinning again might help then.

Chrome 18, ExtJS 4.0 charts issue

I've just updated Chrome from 17 to 18.0.1025.142 and got all the ExtJS charts crashed in the web-site. The same issue reproduces on the Sencha example. Try clicking "Reload data". Any ideas?
I've come across the same problem. It looks like it's a bug in that version of chrome as the dev stream (v19) fixes the problem. It's a total PITA, but hopefully v18 won't be the current version for long. We just disabled the charts for that browser until it's sorted.
Here is an issue opened with chromium. Log in and star the issue so that it goes up in priority for chrome developers.
Also look at this thread for a workaround. Didn't work in my scenario but it might help you.
http://www.sencha.com/forum/showthread.php?192175-4.0.7-Line-Charts-Broken-in-Chrome-18-Mac-(and-also-it-appears-windows)

Why is Dev Tools bar empty?

I'm using Chrome-compatible SRWare Iron 5.0.381 on XP, and was checking out what Chrome has to offer to developers, EG inspecting the contents of the DOM of a currently-loaded web page.
But when I hit CtrlShiftI, the bar is totally empty:
Does someone why this is? Do I need an add-on? Are there other Chrome-compatible tools I should know about?
It appears you’ve found a bug in that fork of Chromium. The inspector works just fine with Google.fr in the latest Google Chrome and Chromium builds. Why don’t you use one of these browsers.
Usually the reason of that is some problem in DevTools JS code.
It is a chance that problem will be solved by chrome restart.
Such kind of problems can happen when chrome is upgrading at background.
The other reason of that can be some changes which you made in DevTools.js.
Of cause if you have done some changes :)
You can troubleshoot such problem by another instance of DevTools.
As example you can try to load DevTools.html page into Safari, open WebInspector for it and check console messages.