-
Notifications
You must be signed in to change notification settings - Fork 46
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
Browser WebGL Creation Fails on NVIDIA #84
Comments
I see the same behavior if I run this on my gaze15 with cosmic-comp set to use the Nvidia GPU for rendering, with With
Signal 11 is SIGSEGV. So it could be a segfault within the driver? But also it shouldn't use GLX on Wayland (it shouldn't be possible to use GLX). So unless that's inaccurately named something's going wrong if it's using GLX rather than EGL. |
Or looking at the Firefox source, maybe it's expected to be prone to segfaults. But anyway, it shouldn't be using glx. // bug 639842 - it's very important to fire this process BEFORE we set up
// error handling. indeed, this process is expected to be crashy, and we
// don't want the user to see its crashes. That's the whole reason for
// doing this in a separate process.
//
// This call will cause a fork and the fork will terminate itself separately
// from the usual shutdown sequence
fire_glxtest_process(); |
Chrome is also dropping to LLVMPipe though more gracefully. Appears this is related to nvidia in general. Issue title updated.
|
Hm, these errors logged to journalctl may be relevant. Or is something worth checking anyway. I see the compositor is still advertising a bunch of formats with the
Edit: Actually, I see there's a comment in Smithay about this call failing being a known issue with Nvidia's driver. And it hopefully shouldn't prevent things from working... |
Okay, so looking at the Firefox code and the bug tracker:
|
Okay, I can
Kind of a strange place to segfault, but consistent with a comment in Firefox's // This is enough to crash some broken NVIDIA prime + Wayland setups, see
// https://github.com/NVIDIA/egl-wayland/issues/41 and bug 1768260.
wl_display_roundtrip(dpy); |
In particular libwayland-client is failing at the line |
Glxtest seems to segfault on sway and Gnome Wayland too, with the Nvidia GPU. Though for some reason the whole Firefox process is failing too when I try it there? So it doesn't seem to be an issue on our end. I guess something is wrong with the Nvidia Wayland EGL implementation. |
NVIDIA/egl-wayland#64 describes a segfault in Firefox in glxtest dereferencing the same thing in |
This appears to be fixed when I build and install https://github.com/NVIDIA/egl-wayland from git. So we should probably be able to package a newer release. |
Actually it seems NVIDIA/egl-wayland@7af7082 is the commit that fixes it, so it's not in the latest release. |
I actually think it's NVIDIA/egl-wayland@c63bf73 that fixes it. Regardless, latest release of egl-wayland still has the issue; a new release should be made. |
NVIDIA RTX A2000 12GB
Driver 525.85.05
From about:support
WebGL 1 Driver Renderer
WebGL creation failed:
WebGL 2 Driver Renderer
WebGL 2 Driver Renderer WebGL creation failed:
Window Protocol
wayland
Desktop Environment
pop:cosmic
Quite a few errors related to blocklisting by glxinfo
#BLOCKLIST_FEATURE_FAILURE_GLXTEST_FAILED
Blocklisted by gfxInfo
Failure Log
No GPUs detected via PCI
glxtest: process failed (received signal 11)
The text was updated successfully, but these errors were encountered: