-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
GL backend crashing #7320
Copy link
Copy link
Open
Labels
A-RenderingDrawing game state to the screenDrawing game state to the screenC-BugAn unexpected or incorrect behaviorAn unexpected or incorrect behaviorO-OpenGLSpecific to the OpenGL render APISpecific to the OpenGL render API
Description
Bevy version
v0.9.1
[Optional] Relevant system information
Debian 11
AdapterInfo { name: "Mesa Intel(R) UHD Graphics 620 (WHL GT2)", vendor: 32902, device: 0, device_type: IntegratedGpu, driver: "", driver_info: "", backend: Gl }
rustc 1.65/1.67
What you did
WGPU_BACKEND=gl cargo run --example custom_skinned_mesh
I was trying to use the gl backend, as I'm encountering issue gfx-rs/naga#1908, with all examples in vulkan seemingly continuing to run in the background, after I close my x11 window with alt+f4.
What went wrong
2023-01-21T22:43:14.498423Z ERROR wgpu::backend::direct: Shader translation error for stage FRAGMENT: gsamplerCubeArrayShadow isn't supported in textureGrad, textureLod or texture with bias
2023-01-21T22:43:14.498458Z ERROR wgpu::backend::direct: Please report it to https://github.com/gfx-rs/naga
2023-01-21T22:43:14.498494Z ERROR wgpu::backend::direct: Handling wgpu errors as fatal by default
thread 'main' panicked at 'wgpu error: Validation Error
Caused by:
In Device::create_render_pipeline
note: label = `pbr_opaque_mesh_pipeline`
Internal error in FRAGMENT shader: gsamplerCubeArrayShadow isn't supported in textureGrad, textureLod or texture with bias
', /home/computermouth/.cargo/registry/src/github.com-1ecc6299db9ec823/wgpu-0.14.2/src/backend/direct.rs:2403:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', /home/computermouth/projects/bevy/crates/bevy_tasks/src/task_pool.rs:273:45
The app crashes. I found this: gfx-rs/wgpu#4455, but it doesn't seem like there's really any action to be taken around it.
Based on people's comments it sounds like intel integrated graphics under x11 are problematic with both vulkan and gl.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
A-RenderingDrawing game state to the screenDrawing game state to the screenC-BugAn unexpected or incorrect behaviorAn unexpected or incorrect behaviorO-OpenGLSpecific to the OpenGL render APISpecific to the OpenGL render API