in both videos i'm scrolling with mouse wheel. after some time, it's unusable laggy.

As per comment #0 we have tested this issue on reported chrome version 66.0.3359.117 and latest chrome stable 67.0.3396.87 using Ubuntu 17.10 as we don't have Ubuntu 18.04.

Steps:
--------
1. Launched chrome
2. Navigated to given URL "www.facebook.com".
3. Navigated to Facebook timeline and navigated to new tab and came back after 20 minutes.
We have observed that the page loading and scrolls normally.

@Reporter: As we are unable to reproduce the issue from  our end.Can you verify this issue with fresh profile that is not having any extensions and apps or reset all the flags.Could you please upgrade your chrome browser and let us if the issue still persists.
You can download latest chrome builds here: "https: //www.chromium.org/getting-involved/dev-channel".

Thanks!

@phanindra
thanks for checking it.

I verified the issue with a fresh profile in another system with the same Version 66.0.3359.117 (Developer Build) built on Debian 9.4, running on Debian 9.4 (64-bit) with the same result. I came out with two questions:

1) could it be that the issue might be related with amd drivers? since both systems have amd cards and drivers.

2) please, correct me if I'm wrong: the link you provided in comment #3 is for getting google chrome, but I am currently running chromium (libre)

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

maildealete@ Thanks for the update.

As per comment #4, as the issue is reproducible on Linux Debian 9.4, adding 'TE-NeedsTriageFromHYD' label and requesting Inhouse team to look into the issue and help in further triaging.

Thanks..

Might be related to  bug 854451 .

Try recording a trace, save it, and attach the result here.
See https://www.chromium.org/developers/how-tos/submitting-a-performance-bug

comment #7: I agree, might be related.
comment #8: thanks. I will.

Yup - trace would be quite helpful.

Here is the trace:
I wasn't sure about which options I needed to check, so I check them all.
the buffer usage reached 100% inmediatly, so I recorded a few seconds starting after the scrolling was already slow, I hope it helps.

https://drive.google.com/file/d/18IvMPOq4vJLX3cI2gjmLsFHmnbrv1Y5R/view?usp=sharing

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

Unable to reproduce this issue on reported version 66.0.3359.117 and latest stable 67.0.3396.99 using debian rodete. Page scroll is normal even after using facebook.com for 15-20 mins.

@Reporter: Could you please check the issue on latest stable and let us know the behavior. You can download it from https://www.chromium.org/getting-involved/dev-channel.

Thanks!

maildealete@: Sorry but the trace you captured has way too much data to sift over with confidence. Could you capture another trace, this time with all the "Record Categories" (left column) checked but none of the "Disabled by Default"  categories (right column).  

Also, could you specify which page you're interacting with in the trace, was it Facebook?

Yes, it was facebook.

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

maildealete@, Thank you but could you please provide a new trace with the "disabled by default" categories all turned off (enabling them adds too much data to the trace) and everything else on.

new trace, made with latest dev from google chrome: Version 69.0.3472.3 (Official Build) dev (64-bit)

and "disabled by default" options disabled. trace recorded while browsing facebook timeline.

Deleted: trace_1.json.gz 5.2 MB

trace_1.json.gz 5.2 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

also, note this CPU usage under Chrome's Task Manager

Deleted: task manager 73.8 KB

task manager 73.8 KB View Download

Thank you.

flackr@, from the trace I see a BeginMainFrame that calls FireAnimationFrame 14,000+ times. Looks like we're somehow stuck in a loop. Could you triage?