| Summary: | [GTK4] Overscrolling causes high CPU usage when navigation gestures are not enabled | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Gabriele Musco <gabmus> | ||||
| Component: | WebKitGTK | Assignee: | Nobody <webkit-unassigned> | ||||
| Status: | RESOLVED FIXED | ||||||
| Severity: | Normal | CC: | alicem, bugs-noreply, gabmus, mcatanzaro | ||||
| Priority: | P2 | ||||||
| Version: | WebKit Nightly Build | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| See Also: | https://bugs.webkit.org/show_bug.cgi?id=243924 | ||||||
| Bug Depends on: | 243924 | ||||||
| Bug Blocks: | 210100 | ||||||
| Attachments: |
|
||||||
It's reproducible in minibrowser as well, so no need for a separate reproducer at this point. :) Hm, I can't reproduce this anymore. Hopefully fixed by https://commits.webkit.org/259530@main. |
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().