It's happenning for a while, i don't remember, whether it happened 2-3 month before.

Most of the time i'm using only the chrome / vs code / android studio. Many time just chrome is opened as i'm learning on youtube. (Google I/O etc.)

So the ubuntu base system (how it handles chrome) or chrome itself can cause the problem.

raxim.uk@ Thanks for the issue.

Tested this issue on Ubuntu 17.10 on the reported version 67.0.3396.87 and unable to reproduce the issue by following the below steps.

1. Launched Chrome and the System Monitor.
2. Navigated to the webpage and moved the cursor, cannot see any increase in the CPU usage.
Attached is the screen cast for reference.

Request you to check and confirm if anything is missed from our end in triaging the issue.

Also request you to retry the issue on a new chrome profile without any flags/extensions and update the thread with the behavior.

Thanks..

Deleted: 854805.webm 20.8 MB

854805.webm 20.8 MB Download

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

First of all the long supported version of ubuntu is 16.4, not the 17.10 (short term supported variant)

I cannot show you the page, because it's under development, but if you look at the top bar. (red circle) You can see the heavy CPU usage. When i'm moving somewhere else it suddenly stops.

I moved cursor on html elements in the inspector window! When i moved to the area of the page, it suddenly stopped. I have a CPU with a noise so i know when it happens.

There is a race condition, as it does not happen on all the screen, when i looked at lately.

My screen might be heavy, uses a self-made virtual scroll, but working smoothly on mobile device without causing any big CPU usage at default.

Virtual scroll = you have for example 10 div slot, what you are moving on the screen, but not rendering all the element what you have loaded. (for example - https://ionicframework.com/docs/api/components/virtual-scroll/VirtualScroll/)

The issue is definitely there somewhere.

Deleted: Screenshot from 2018-06-21 14-00-47.png 629 KB

	Screenshot from 2018-06-21 14-00-47.png 629 KB View Download

http://m.privatbankar.hu/ might be not the right example, because the cpu usage is not constant - but if you move the cursor constantly down and up on html elements in the inspector window, problem happens.

I can't reproduce this in any way.

You can try recording a trace with chrome://tracing when this happens and send it to us, but it looks like it has something to do with your environment.

I'm not sure what i have done, but that's the web developer stuff

Deleted: trace_inspector_trace.json.gz 5.3 MB

trace_inspector_trace.json.gz 5.3 MB Download

Able to reproduce the issue on Mac 10.13.3, Win-10 and Ubuntu 17.10 using chrome reported version #67.0.3396.87 and latest canary #69.0.3472.3.
This is a non-regression issue as it is observed from M60 old builds. Attaching screen cast for reference.

Hence, marking it as untriaged to get more inputs from dev team.

Thanks...!!