-
-
Notifications
You must be signed in to change notification settings - Fork 790
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
Input lag on HiDPI 4K when maximizing window #4110
Comments
FWIW, the resize crash is from the upstream wgpu crate: |
Can you clarify what you mean by 500ms of input lag? Are you saying that every key press takes 500ms to render? |
Exactly. The time between key press and rendering. Update: I've tried to measure it with the slomo mode of my camera, which puts it more in the 200+-50 ms ballpark for maximised window and 100 ms for full screen.
Independent of applications and shells (in WSL2!) and also in the debug overlay. |
I am also having this issue on Fedora 41 KDE with wezterm 20241104_083404_51c794ac. Maximizing the window on 4K screen really increases the CPU usage used by wezterm and it becomes slow to respond. Resize it to a smaller window and cpu usage and lag also scale down. |
What Operating System(s) are you seeing this problem on?
Windows
Which Wayland compositor or X11 Window manager(s) are you using?
Windows 10
WezTerm version
20230712-072601-f4abf8fd
Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?
No, and I'll explain why below
Describe the bug
I experience a noticeable input lag (up to estimated 500 ms) proportional to the size of the window and of the screen resolution (when I move a window between displays of different resolutions). This is true for both WebGPU and OpenGL mode. The performance on Dx12 is much better than with Vulkan backend.
However, it feels to me, in fullscreen (without decorator) the lag is smaller again even on 4K resolution.
I am on a Intel(R) Core(TM) i7-8565U CPU with integrated Intel GPU. Is it too weak?
I tried the current nightly (20230712-072601-f4abf8fd), but it crashed when resizing the window.
On my, admittedly substantially beefier, Linux machine I have no issues.
To Reproduce
Open a new window, type, observe lag between pressing key and appearance of the character on the screen.
Configuration
Expected Behavior
No (noticable) input lag, even on slightly dated laptop hardware.
Logs
Anything else?
Thx for making Wezterm. I ❤️ it!
The text was updated successfully, but these errors were encountered: