-
-
Notifications
You must be signed in to change notification settings - Fork 808
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
Wezterm crashes while using WebGPU backend with NVIDIA 560 drivers #6050
Comments
Having a similar issue on NixOS, using mutter as my compositor. My nvidia driver version is 560.35.03.
That's what I have in my logs. When I launch it from the CLI, I get a SIGV (Address Boundary Error). I assume it has to do with wayland / Nvidia / explicit sync, but I'm not too sure how to troubleshoot it. |
Seems the same issue as I'm having in #6060 ,
|
Nvidia drivers being a huge headache again... I can't isolate the issue as well as I want to since wezterm's rendering is also currently broken in nixpkgs . There is definitely something wrong with the latest Nvidia drivers (very likely related to explicit sync, as it seemed to be a common error I get whenever enabling wayland in the config).
EDIT: It seems to be also happening on my amdgpu laptop. Here's the wezterm crash log I'm getting:
This is happening with
I'm unsure if this is expected behavior, as I'm using my laptop's integrated graphics with those (AMD 7040 series). |
It looks like a wgpu 0.18 incompatibility with the new explicit sync. Can't really report it to wgpu since they probably won't even take a look given it's a 1 year old version. wezterm would have to be updated to use newest wgpu before reporting. |
Extra comment: last time older wgpu versions were broken with new NVIDIA drivers, NVIDIA patched it without apps needing to update wgpu, so might be worth reporting to NVIDIA. |
So one of the fixes we could look into would be updating the version of wgpu wezterm uses? I assume this might imply breaking other things however.. |
Yep, I've just done testing based off #5814 (branch wgpu-020) and the issue does not occur on that version of wgpu. I'm sure there are some other issues with that branch but runs fine for me so I'm probably gonna run it until main catches up and/or NVIDIA patch it. @wez any chance that PR could progress given that wgpu 0.18 is now fundamentally borked on NVIDIA 560 on Wayland? I would help personally but I'm not familiar with wezterm/wgpu internals. I am getting the same issue as you were getting if I run it under XWayland (transparent window) but runs completely fine under native Wayland. |
On KDE wayland + NVidia, I received the error when using WebGpu frontend
The workaround for me is using enable_wayland = true,
front_end = "OpenGL", |
Thank you! This solved my issue. |
Does that branch work for you? Trying to run it, I'm getting:
I'm also using the nix flake so that might be related. |
FWIW, I just pushed 09ac8c5 to |
I can confirm works for me with the latest main (9bf30b8), many thanks |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
What Operating System(s) are you seeing this problem on?
Linux Wayland
Which Wayland compositor or X11 Window manager(s) are you using?
Hyrpland
WezTerm version
20240812-215703-30345b36
Did you try the latest nightly build to see if the issue is better (or worse!) than your current version?
Yes, and I updated the version box above to show the version of the nightly that I tried
Describe the bug
I'm not sure if it's related to nvidia driver updates but today I started my pc and saw wezterm getting closed automatically around 30~ seconds after its start. Reverting backend to the OpenGL fixed the issue on my side.
OS: EndeavourOs
WM: Hyprland (Wayland)
Nvidia Driver Version: NVIDIA 560.35.03
To Reproduce
No response
Configuration
no config
Expected Behavior
No response
Logs
Anything else?
No response
The text was updated successfully, but these errors were encountered: