Chrome freezes on hotreload after clientside js change while devtools open

klabauter · 2018-09-18T12:16:06.419Z

So this error suddently occurs to me everytime I change something in my clientside code.
I don’t think this is a Meteor issue, but since the refresh of the browser is triggered by Meteor I figured I would ask here if someone has the same problem?!
Tried rebooting my whole system, installed an older chrome version but the problem is still there:

When I change something in my clientside code while I am in my app on localhost in Chrome and while having the Chrome devtools open, the whole Chrome tab freezes for a couple of seconds and then reloads. During that time, Chrome uses like 300% of my cpu. dafuq? Anyone ever had that? Tried emptying my cache and everything I could think of but nothing helps!

robfallows · 2018-09-18T12:26:36.399Z

I’ve never seen that. What version of Chrome are you using?

klabauter · 2018-09-18T12:38:09.143Z

Version history: https://en.wikipedia.org/wiki/Google_Chrome_version_history
I had 69.0.3497, now I am running 68.0.3440 again which improved the problem a bit.
OS is Mac OSX.
No idea why this is happening.

robfallows · 2018-09-18T14:22:13.447Z

Memory issues?

Does the Chrome Task Manager (shift-Esc) reveal anything here?

klabauter · 2018-09-18T14:33:43.895Z

Nope, not possible. 16GB RAM and never had any problems. Occurred out of nowhere today.
Yes, Chrome task manager reports 300% COU usage of the one tab during freeze.

minhna · 2018-09-18T14:43:23.825Z

I had this problem. But not very often.
I use chrome on Linux Ubuntu 18.04.

tosi · 2019-09-29T20:51:04.606Z

I have this problem now :). I installed all stuff on a new computer, the Chrome recently updated and I finished full Windows Linux Subsystem integration (VS Code does “remote” access), so there are many possible culprits.

Chrome version: 77.0.3865.90
Meteor runs from within Ubuntu 18 on Windows Linux Subsystem.

Symptoms: Chrome tab usage 300%, way way higher than anything else. Chrome stops responding… this gets “fixed” after ~20-100s and the page finally refreshes. Only happens when devtools are open. Restarting Windows helps for a few minutes (or turning off the dev tools).

lalomores · 2019-10-01T21:04:34.268Z

Same with Meteor 1.8.1, Chrome Versión 76.0.3809.132 (Build oficial) (64 bits).
It was happening with Meteor 1.6 as well and I was hoping the upgrade was going to fix it.
I’ve also found some infamous “Major GC” process going if profiling the performance with the devtools.
The strange thing after the upgrade is that now many times I change something in a component (inside a client folder, so client only) and Meteor fails to acknowledge the client refresh. Takes some time, app looses connection, couple of page refreshes and finally gets back. It may very well fit the 20-100s period @tosi is reporting.

Modifying client only stuff is now excruciatingly long.

tosi · 2019-10-02T06:26:25.679Z

It looks like there is a workaround to install Chrome Beta 78. There are also no addons so it might be related. I will try to find the real culprit.