-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
two_passes example breaking on Windows #11755
Copy link
Copy link
Closed
Labels
A-RenderingDrawing game state to the screenDrawing game state to the screenC-BugAn unexpected or incorrect behaviorAn unexpected or incorrect behavior
Milestone
Description
Bevy version
Main (f514d5c)
Relevant system information
AdapterInfo { name: "AMD Radeon RX 6750 XT", vendor: 4098, device: 29663, device_type: DiscreteGpu, driver: "AMD proprietary driver", driver_info: "24.1.1 (AMD proprietary shader compiler)", backend: Vulkan }
SystemInfo { os: "Windows 11 Pro", kernel: "22631", cpu: "", core_count: "6", memory: "31.9 GiB" }
What you did
cargo run --example two_passes
What went wrong
Sometimes it crashes (in 5 runs, crashes 2 times). The problem is only on startup, after that, seems to be working fine.
thread '<unnamed>' panicked at crates\bevy_core_pipeline\src\msaa_writeback.rs:83:18:
called `Option::unwrap()` on a `None` value
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Encountered a panic in exclusive system `bevy_render::renderer::render_system`!
thread 'Compute Task Pool (5)' panicked at crates\bevy_render\src\pipelined_rendering.rs:145:45:
called `Result::unwrap()` on an `Err` value: RecvError
error: process didn't exit successfully: `target\debug\examples\two_passes.exe` (exit code: 101)
Additional information
Seems to be related to #10812, since it works fine on commit 7705c1d but breaks on 9f7e61b
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 behavior