Encoder is invalid in example on macOS #20844
Description
Bevy version and features
Latest main
[Optional] Relevant system information
I am running the latest macOS 26 beta.
What you did
Run the log_diagnostics example on main:
Running `target/debug/examples/log_diagnostics`
2025-09-03T11:39:22.415400Z INFO bevy_diagnostic::system_information_diagnostics_plugin::internal: SystemInfo { os: "macOS 26.0", kernel: "25.0.0", cpu: "Apple M3", core_count: "8", memory: "16.0 GiB" }
2025-09-03T11:39:22.487064Z INFO bevy_render::renderer: AdapterInfo { name: "Apple M3", vendor: 0, device: 0, device_type: IntegratedGpu, driver: "", driver_info: "", backend: Metal }
2025-09-03T11:39:22.737421Z INFO bevy_render::batching::gpu_preprocessing: GPU preprocessing is fully supported on this device.
2025-09-03T11:39:22.773936Z INFO bevy_winit::system: Creating new window log_diagnostics (0v0)
2025-09-03T11:39:23.720897Z ERROR wgpu::backend::wgpu_core: Handling wgpu errors as fatal by default
thread '<unnamed>' panicked at /Users/olle/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/wgpu-26.0.1/src/backend/wgpu_core.rs:2391:18:
wgpu error: Validation Error
Caused by:
In a CommandEncoder
In a pass parameter
Encoder is invalid
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Encountered a panic in system `bevy_render::renderer::render_system`!
What went wrong
Panics immediately, instead of having a working example.
Additional information
I discovered this while working on #20802, so at first I thought it was my code, but then I tested it on main and it persisted.
We might need to isolate the issue to find out if it's macOS (and maybe even macOS 26) specific.