[Crash] STATUS_STACK_BUFFER_OVERRUN (0xc0000409) on startup with RTX 4060 Ti (Solari)
- Dominant language
- Rust
- Stars
- 48.2k
- Forks
- 4.8k
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 171
Description
# Bug Report Draft: STATUS_STACK_BUFFER_OVERRUN on Windows 10
**Title:** [Crash] STATUS_STACK_BUFFER_OVERRUN (0xc0000409) on startup with RTX 4060 Ti (Windows 10, Vulkan)
**Description:**
I encountered a persistent crash (`STATUS_STACK_BUFFER_OVERRUN`) when trying to run `bevy_solari` 0.18.0-rc.2 with Bevy 0.18.0-rc.2 on Windows 10. The application crashes immediately upon rendering the first frame if `SolariLighting` and `CameraMainTextureUsages::STORAGE_BINDING` are enabled.
**Environment:**
- **OS:** Windows 10 Pro (Build 19045)
- **GPU:** NVIDIA GeForce RTX 4060 Ti (Driver: 591.74)
- **Rust:** 1.83.0 (stable-x86_64-pc-windows-msvc)
- **Bevy:** 0.18.0-rc.2
- **bevy_solari:** 0.18.0-rc.2
- **Backend:** Vulkan (Default)
**Reproduction Steps:**
1. Setup a standard Bevy 0.18 app.
2. Add `SolariPlugins`.
3. Spawn a `Camera3d` with:
```rust
CameraMainTextureUsages(TextureUsages::RENDER_ATTACHMENT | TextureUsages::STORAGE_BINDING),
Msaa::Off,
SolariLighting { reset: true, ..default() },
```
4. `cargo run`
5. Process exits with code `0xc0000409` (STATUS_STACK_BUFFER_OVERRUN).
**Troubleshooting Attempts (All Failed):**
- Increased stack size via `RUST_MIN_STACK=104857600`.
- Switched to DX12 backend (Panic: `UnsupportedFeature`).
- Disabled `dlss` feature.
- Manually generated tangents and `RaytracingMesh3d` for all meshes.
- Increased WGPU limits (textures/storage).
**Logs:**
No panic message is printed to stdout/stderr. The process simply terminates with exit code `0xc0000409`.
**Context:**
Reverting to standard PBR (removing `SolariLighting` and `STORAGE_BINDING`) resolves the crash immediately.
Contributor guide
Research direction
Start by reproducing the crash with bevy_solari 0.18.0-rc.2 on Windows 10, Vulkan, and an RTX 4060 Ti using SolariLighting with STORAGE_BINDING enabled. Compare the failing configuration with standard PBR, which reportedly avoids the crash, and verify completion when the startup crash is resolved without those workarounds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- computer-graphics, game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100