Chrome randomly pegs CPU to 100% usage for 5 seconds when opening or closing a tab

[Rowsol]

I checked firefox and edge. The problem is solely with chrome. I disabled all addons - problem persists.

I want to say it started happening after upgrading my graphics card to a 1650 super. I installed new drivers for it, started getting weird issues such as display adapter stopped responding so I uninstalled the drivers, restarted in safe mode and installed there. Everything has been good since but Chrome has turned to shit. This could all be coincidence but I don't think it is.

To elaborate - If I open about 10 tabs and start closing each one by one I'll likely have a 5 second freeze upon closing one of them. If I right click and choose to close all tabs it never happens.

 

[FreedomEclipse]

Just chrome being chrome sadly.... I think they had a recent update which messed up some things.

 

[Bill_Bright]

Just chrome being chrome sadly....

I have to agree. I've seen this many times on multiple systems with Chrome. Chances are if you look in Task Manager, you will see many Chrome sessions too. This is actually one reason I switched to Pale Moon as my primary/default browser several years ago (though now my default is the new Chromium based Edge - which, BTW, supports almost all Chrome extensions).

If rebooting does not resolve your Chrome problem (for awhile), you can try uninstalling Chrome, rebooting, and reinstalling it. But again, that's no guarantee the problem won't return.

 

[P4-630]

Hmmm, no issues here on my i3 7100U laptop.

 

[natr0n]

As a firefox user never have issues.Occasionly graphic glitches displaying a site, but driver related. Chrome is resource hungry though.

 

[XL-R8R]

I think you'll find its probably down to the "software_reporter_tool.exe" being a bit silly and checking for extensions among other things.




Disabling this exe seemingly does nothing as it will only spawn another instance of its self or patch the missing files... following my own common sense - along with guides posted at various sites online - did not resolve this for me; closing the exe via taskmanger when the spike in CPU usage is noticed is the 'cure' so far.









Edit before the bashing of Chrome begins to suggest that the people with those intentions find a better place to be on a Sunday than whining on a digital forum.