Bug 245616 - [GTK4] Overscrolling causes high CPU usage when navigation gestures are not enabled
Summary: [GTK4] Overscrolling causes high CPU usage when navigation gestures are not e...
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKitGTK (show other bugs)
Version: WebKit Nightly Build
Hardware: PC Linux
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on: 243924
Blocks: GTK4
  Show dependency tree / graph
 
Reported: 2022-09-24 04:46 PDT by Gabriele Musco
Modified: 2023-09-08 13:40 PDT (History)
4 users (show)

See Also:

Attachments
Minimal bug reproducer (851 bytes, text/x-python)
2022-09-24 04:46 PDT, Gabriele Musco 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Gabriele Musco 2022-09-24 04:46:34 PDT 
Created attachment 462579 [details]
Minimal bug reproducer

As the title says, overscrolling beyond the page limit either up or down causes high CPU usage. This goes away if scrolling back up/down after overscrolling.

This does not happen when enabling enable_back_forward_navigation_gestures.

It can be reproduced with minibrowser, as well as a minimal reproducer I'm attaching to the issue.

To see the issue go away in the reproducer attached uncomment the line saying self.enable_gestures().
Comment 1 Alice Mikhaylenko 2022-09-24 04:49:19 PDT 
It's reproducible in minibrowser as well, so no need for a separate reproducer at this point. :)
Comment 2 Alice Mikhaylenko 2022-11-23 19:25:34 PST 
Hm, I can't reproduce this anymore.
Comment 3 Michael Catanzaro 2023-01-29 06:12:58 PST 
Hopefully fixed by https://commits.webkit.org/259530@main.