This happens recently in my Chrome's source panel. It used to work just fine. Not sure if that's causing by the recent update of Chrome (I'm currently using 68.0.3440.106 (Official Build) (64-bit) on macOS High Sierra 10.13.6)
As you can see in the screenshot, these are all the locations that I can set breakpoints in this file. Normally, you can at least set breakpoints at line 6-10 but now, I can only set at line 8. Why?
Anyone who is also experiencing this?
Update: This also happens on my Windows machine with the same 68.0.3440.106 Build.
Related
I have noticed some weird behavior in Chrome Dev Tools in at least the current build I have and possibly a few others before...
This is my current Chrome Version: Version 78.0.3904.87 (Official Build) (64-bit)
So what happens is I open Dev Tools using F12, click elements, select an element to view using the element selector and then at some point for seemingly no reason, it switches to Sources. This happens over and over again. Basically I am trying to do something with the element and then it suddenly switches to sources within 10 seconds and usually to some random weird js file.
No idea why this is happening, and it just started recently, within the past 2 weeks. It is literally driving me crazy because I like to play around with styles on elements in the HTML to see what they will do at times.
Any suggestions or is this some bug in Chrome now?
I recently updated Google Chrome to the 61.0.3163.79 version and it was suddenly very slow with canvas. This issue only appears on Linux.
For exemple, http://vincentgarreau.com/particles.js/ was 60 FPS before the Chrome update, and now it run at 2 FPS.
What's wrong with the new Google Chrome update ?
P.S: Chromium 61.0.3163.79 works fine on my computer.
I found workaround. After upgrade Chrome to 61 version I faced same experience with you.
Try adjust following chrome flag to Disabled.
chrome://flags/#enable-color-correct-rendering
I expect Default flag have different means with before 61 version.
Below the result is in my case on attached url from you.
Default - 5 fps
Disabled - 35 fps
I wish this help you.
The enable-color-correct-rendering flag does not exist after upgrade to Chromium 62.
Fortunately the slowness disappeared after setting flag
chrome://flags/#force-color-profile to sRGB as mentioned on google forums
Tested on Chromium 62.0.3202.75, 64-bit, Linux
The solution for me was disabling Use hardware acceleration when available setting:
Chrome menu > Settings > Show advanced settings > Scroll down to "System" > Uncheck "Use hardware acceleration when available"
Source
I had the same problem with Version 69.0.3497.81 (Official Build) (64-bit).
I tried all already proposed combinations of enabling/disabling features from chrome://flags. But they didn't work for me.
To me helped enabling of these 2 flags:
chrome://flags/#ignore-gpu-blacklist
chrome://flags/#enable-draw-occlusion
Improved performance of canvas 2D renderings dramatically
Chrome itself appears to work fine but I'm having problems with Developers Tools. After a short period of time it becomes unresponsive and the following dialog pops up...
Is this a known bug, can or will it be fixed soon? Also, the meantime what should I do, how can I roll back to older working version of Chrome?
I use Chrome and Developer Tools extensively and this is causing a major headache, so any advise would be welcome.
It is a known bug that got pushed with v32. I have not seen anything about fixing it yet though.
It happens with any model window (which includes devtools) or when Chrome is running in app mode.
Chrome isn't actually crashing and you can still continue to use it, but that will continually pop up with devtools open.
The issue has been fixed as of today's (1/28/2014) update. Version: 32.0.1700.102 m
I started getting this problem as well.
In searching, I came across this issue: "Page(s) Unresponsive" error messages in 32+.
As best I figured out, the bug is related to:
Windows 7/8 with Aero Theme
Scrollbars on pages (such as in the developer console)
Pages with popups (in particular Window.open() calls)
I guess they are slated to push the fix into version 33...and maybe leave the stable* 32 how it is (I hope not).
So there are a few options:
Switch away from Aero Theme until version 33 is in stable
Upgrade to the beta channel, i.e. version 33
Click on the Wait button every 30 seconds whenever the chrome developer tools is open (Don't try this at home).
Update:
Chrome has released a hotfix into the version 32 stable channel.
The issue is resolved in Chrome Canary 34.0.1799.0. Read more:
Issue 335248: "Page(s) Unresponsive" error messages in 32+
#elewinso, Alternate place to look for the same registry key to disable Chrome autoupdate is HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Google\Update..
Also, is there a way I can get notified when the next update happens? or, when can I remove this key?
upgrade chrome to Version 32.0.1700.102 m this fixes the problem
It appears that the excellent carousel library ContentFlow has reflection issues with Chrome on Mac (I am using Lion). Seems to be fine on PC. Visit http://www.jacksasylum.eu/ContentFlow/ in Chrome and you'll see in the example the images are incorrectly mirrored with a shady part at the top as per the below screenshots. Is there a fix / workaround? It doesn't seem that there is active development on ContentFlow anymore, which is a shame.
I'm using Chrome 16.0.912.75, on Mac (Lion)
****EDIT**** Screenshots
Proper (from Safari)
Broken (from Chrome)
There's an issue open here: http://code.google.com/p/contentflow/issues/detail?id=34
People tried different things, but it breaks on Windows' Chrome :(
I have some code that I thought I had written so that it would play nice on IE. But apparently it does not. I use IE8 for my testing and get quite frustrated with the built-in debugging 'tool'. I found that firebug has a javascript tool that debugs for IE but I have to click it for every page, wait for it to load and then test my script. Is there a way to make IE ALWAYS load the firebug .js file? I tried searching for way to set up a custom header file for my IE installation but was unsuccessful.
Is there another tool out there that would be better/easier to use? Another way to test scripts for IE compatibility?
IE7 and 8 provided the IE developer toolbar. This is similar to firebug for DOM inspection, script debugging and style tracing.
Edit:
For IE 8, the toolbar is already packaged with the browser:
The Developer Toolbar is not compatible with Internet Explorer 8. Please use the developer tools included with Internet Explorer 8. Press F12 or click the 'Developer Tools' entry in the Tools menu to begin using the tool. Click here for more information on IE8 Developer Tools.
You can also use Visual Studio and attach to the process in question, then just debug in VS. Pretty good debugging tools, and lets you debug IE6 as well.
Try my log4javascript, which is a logging library that works in every major browser, including IE 5 and later.