New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
webview lags when zooming quickly #4628
Comments
I've run into the same issue, but it's much more pronounced. It's taking several seconds to switch to a zoom level which hasn't been rendered yet. To my surprise, it's almost instant when switching back, which I guess is caused by some sort of cache of the zoomed layout. (Recorded with
```
qutebrowser v1.13.1
Git commit:
Backend: QtWebEngine (Chromium 77.0.3865.129)
Qt: 5.14.2
|
@Jumblemuddle Can you check how things look in Chromium and/or in other QtWebEngine browsers such as Falkon? |
I haven't actually been noticing as large delays when zooming lately, but I'm not sure what changed. |
I'm still noticing large delays when using the zoom feature, so I'd say this issue is still legitimate to be open and still being a problem it is very hard for me to use the zoom feature since it tries to redraw eveerytime the zoom level changed, but I'd like to reach like 200% directly not wait for the rendering of the in-between for like 10 seconds then reach the right zoom level being rendered, finally. |
Note you can press |
I have the exact same issue. Zooming with Ctrl + Scroll Wheel will make QB unusable until it stops rendering. Being the increment with scroll wheel very fine it's much more laggy than using |
Version info (see
:version
):Does the bug happen if you start with
--temp-basedir
? (if applicable):Yes
Description
When scrolling quickly, the webview can lock up (this is worse on slower computers). It seems that this is due to 2 slow config calls and displaying (and logging) info messages.
It should be trivial to disable info messages on zoom and fix the config calls, but does that (by default) sound like a good idea?
How to reproduce
https://youtu.be/K61o1HolnmQ
The text was updated successfully, but these errors were encountered: