After Chrome update to version 60, my application (Typescript + React) works very slowly. Using Performance tab in Chrome Dev Tools, I found out that the browser takes sick time rendering elements (the Layout process).
Summary time graph here
Has anyone encountered such problem? What could possibly cause this? The code is the same for sure, I have checked once more on two different versions of Chrome. I am running out of ideas.
After version 60, when I opened a new browser window (Ctrl-N or Ctrl-Shift-N) I had everything inside Chrome totally SLOW, even typing.
I solved it disabling option "Use hardware acceleration when available" in Chrome settings.
Cheers
PS: I am using Linux Mint 18 sarah
Related
Been googling around a bit for the last week or two and haven't come up with any leads.
I believe this started ever since the latest major chrome web browser update, from 68 to 69. (currently on version 69.0.3497.100 )
Basically, when I'm using the chrome dev tools and debugging some javascript, the browser crashes when I begin typing a variable name into the console. I'll get a character or two in and then bam, the whole thing crashes.
I'll close the browser, reopen it and still crashes immediately when typing in the console. Sometimes there are a few hours in between episodes, but this has been a persistent issue for too long and is severely impacting my ability as a developer.
Any help would be greatly appreciated. Thanks.
As pointed out on this Reddit post: Google Chrome 69 Issues, that particular version was riddled with bugs. One website, quoting here from the same reddit thread, titled their article as "Atrocious performance - Google Chrome 69".
While this is not a solution, the easiest thing you can do is update to the latest version. (70.0.3538.77, at the time of writing.)
Safari 11 is crashing when i open web inspector. Odd thing is, It works without failing if i don't open console panel. My HTML5 application works well in all other browsers.
There is no memory leaks as it is not going beyond 50MB while taking memory heaps. And no use of console methods.
Is this a known issue in Safari 11?
The only thing I can do to fix this is free up RAM. If I close a few applications and then try it again, it always works. Also after it crashes a few times you will not be able to inspect your device until you quit safari completely and open it again.
Some say it seems to be an hardware issue, happening only when the battery is at 100%.
Have a closer look here:
https://forums.developer.apple.com/thread/92290
Maybe it helps keeping on your flashlight and camera, then establishing a cable connection and starting the web inspector then.
Anyway: This wasn't working for me.
Another Maybe: Connect via network instead of a cable connection.
Things that might be too late by now:
Advice 1: Do not upgrade above 10.x and use Safari 10.x along with iOS 10.x
Advice 2: Put your devices in trash or sell it anyway and start not to use apple anymore. 99% of my upsets lead to issues with iOS and Mac.
a long time we are developing one webapplication, that was running fine on Chrome 56. After Chrome upgrade on version 57.0.2987.* we are encountering a big problem. Sometimes if I'm moving with mouse, some errors will apears:
when this erros will apears, we cannot click on some functions like this:
it will generate another error:
so our application is in this state useless.
However, after refresh is all fine, after another refresh can this errors apears again. We don't know how to exactly simulate this bug.
Did someone encounter any similar problem?
PS: I'm not developer of this webapp, but if you need any other info, just ask. First I was asking here
Edit: On chrome 56 it works, on beta chrome 58 it works too without these errors.
It was just creepy version of Chrome. These errors was only on Chrome version 57. Other versions are ok. Even Google released version 58 faster, then it was expected.
I have a large, javascript heavy web app that I am working on. I am experiencing very slow response times from Chrome Dev Tools for XHR responses and console loggging (3-5 secs). The actual app is running fast and responsive, only dev tools looks like it is suffering.
Does anyone have any idea why Chrome Dev Tools is becoming sluggish as my app grows?
Devtools are like any other debugger; they hook into the normal processing flow of an application, and store quite a bit more information than is normally required. This is much more work than simply rendering the page without debugging enabled, so it will indeed be slower.
That said, 3 seconds to respond to console.log seems high. I'd suggest that you first test the application in a nightly version of WebKit. If it's responsive in WebKit, but not in Chrome, please file a bug against the inspector via http://new.crbug.com/ along with any information you can provide about what scenario causes the slowness.
If it's equally sluggish in WebKit, please file a bug against WebKit's Inspector component: https://bugs.webkit.org/enter_bug.cgi
Either way, post the bug ID here, and I'll see that it's triaged into the correct team.
I "fixed" the slow chrome developer tool by (under SOURCES tab)
clearing the "watch" list that accumulated over time...
clearing all the "snippets", i had dozens as well...
Not sure which of both made the most difference, but it certainly made a difference
This is an old question, but it may help someone landing here later like I did.
Using Chrome 46.x/47.x on Linux (RHEL 7), none of the proposed solutions worked for me. What did work was to disable the setting "Use hardware acceleration when available", in the advanced browser settings.
I noticed in the process monitor/list that the Chrome renderer was taking up a lot of CPU, even putting a breakpoint or stepping throught statements in the debugger would take 10+ seconds!
Might be worth a shot.
Undock the developer tools into separate window.
In my case, it's work.
I struggled with this also, to the point where stepping through code using the chrome debugger was just so slow it took hours away from my productive development time. In watching the CPU utilization when debugging in chrome I would see it use up to as much at 40% of all 4 cores of my processor. I tried everything to no avail. Finally, I tried making the browser window of the page I was debugging as small as I could without losing any of the required view and miraculously it solved the problem. So, now I keep my debugger window popped out in a separate window, and make the window of the page I am debugging as small as I can and my debugging experience is very fast again. I have tested this over a period of weeks and it has held out. Hope this helps someone.
I build this
http://ipl.janstudt.de/
website which is supposed to run on the iPad (it does) and in Google Chrome. In Chrome (on Win 7 64bit), after a seemingly random time of a few minutes, the browser freezes. Also, sometimes when I click the "Reload Page" button in Chrome while on this site, the Browser also freezes. In both cases, the Browser recovers after 10-20 seconds.
How do I get to the bottom of this? There are no Javascript Errors. The memory footprint is very modest and does not increase over time (according to the heap snapshots). There are no plugins involved.
I really doubt it is your script; rather, I think it is Chrome doing something silly. I would test it on other similar systems to see if you can reproduce it. I've had it running on mine for about 5 minutes with no issues (Win7, 64bit, Chrome 5.0.375.127).
You could try to keep the profiler running and catch the freeze-up, but I think that would just be a waste of time.
Landed here while dealing with similar issue. Got a solution by changing hardware acceleration settings
FYI:
https://productforums.google.com/d/msg/chrome/daV0DhOXKVI/oBPZ6pUtBgAJ