Thanks for filing the issue!

Unable to reproduce the issue on reported chrome version 65.0.3325.162 using Ubuntu 14.04 with the below mentioned steps.
1. Launched Chrome
2. Loaded http://www.bbc.com/,https://twitter.com/login?lang=en,https://login.yahoo.com/ and a few other tabs along with https://www.google.co.in/maps
3. Used Google maps(for few hours) while other sites are open in other tabs.
We didn't notice any lag or slowness in its functioning and CPU usuage while the above steps are being performed.

@Reporter: Could you please let us know if we have missed anything in the process. Could you please check the issue in a new profile with out any apps and extensions in it and let us know if the lag/slowness is still seen. Any further inputs from your end may help us.

++Point no.2- spacing: http://www.bbc.com/, https://twitter.com/login?lang=en, https://login.yahoo.com/

I forgot to mention (totally my bad): I don't know of a way to systematically reproduce it, it just happens every once in a while, usually after using Chrome for very long (usually I don't ever even close it, just leave it open, and I don't reboot my computer very often, just suspend it or even leave it turned on while not using it).

> Could you please check the issue in a new profile 

Unfortunately that's not going to happen, as I would have to start using the new profile regularly in hoping to [not] observe the issue maybe after a week or a month.

Regarding extensions, the only two I have are these, which I strongly doubt can interfere, as they hardly do anything at all while not being actively used (and I usually don't). I'll disable them completely and see if I observe the issue again soon.


Given the intrinsic difficulty in reproducing the issue, maybe in the meantime can you tell me, if there's anything I can do the next time I observe it, in order to collect any data that may be useful in investigating it? Remember that restarting Chrome makes the issue go away, so anything involving starting Chrome with a flag wouldn't be viable.

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Checked the issue on reported chrome version 65.0.3325.162 using Ubuntu 17.10 with the steps mentioned in C#2, still we couldn't find any slowness and the CPU usage was normal.

As we are unable to reproduce the issue from our end, Hence removing Needs-Bisect label and requesting someone from UI team to have a look into it and help in further triaging the issue.

Thanks!

Tentatively adding Performance-Power label as this is related to CPU performance related issue. Could someone from dev team please have a look into this issue.

Thanks!

I have just experienced a case where this was triggered by linkedin and not Google Maps. 
I had booted few minutes earlier and I hadn't opened Google Maps ever. Then I opened LinkedIn on a tab and Chrome started consuming around 100% CPU or more and Xorg too.

In this case, even closing Chrome didn't cause Xorg to stop consuming around 100% CPU. I had to kill Xorg.

So, whether or not there is a bug in Chrome, there is definitely a bug in Xorg too involved.

As the issue is not seen from our end, hence adding label "TE-NeedsTriageHelp" and requesting someone from Dev team to have a look into it and help in further triaging.

Thanks!

For fuck's sake guys, this deserves some attention...

Still experiencing the issue from time to time.

Sick of it.

One months without anybody even saying anything.

Bug still there.

Still pretty fucking annoying.