Window crashes when using hotpatching with wgpu on Windows
- Dominant language
- Rust
- Stars
- 48.2k
- Forks
- 4.8k
- Avg merge
- 3d 22h
- Merged PRs (30d)
- 161
Description
bevy: 0.19.0
dx: 0.7.10
os: Windows 10
Running it directly results in the following 0xc0000005 error.
```
dx serve --hot-patch --features "bevy/hotpatching"
09:03:43 [dev] -----------------------------------------------------------------
Serving your app: bevy_exmaple! 🚀
• Press `ctrl+c` to exit the server
• Press `r` to rebuild the app
• Press `p` to toggle automatic rebuilds
• Press `v` to toggle verbose logging
• Press `/` for more commands and shortcuts
----------------------------------------------------------------
09:03:55 [dev] Build completed successfully in 12.54s, launching app! 💫
09:03:56 [windows] 2026-08-13T01:03:56.196145Z INFO bevy_diagnostic::system_information_diagnostics_plugin::internal: SystemInfo { os: "Windows 10 Pro", kernel: "19045", cpu: "12th Gen Intel(R) Core(TM) i5-12400", core_count: "6", memory: "31.8 GiB" }
09:03:58 [dev] Application [windows] exited with error: exit code: 0xc0000005
```
but all works fine after switching to the DX12 backend
```
$env:WGPU_BACKEND="dx12"
```
Contributor guide
Research direction
Reproduce on Windows 10 with Bevy 0.19.0 and dx 0.7.10 using `dx serve --hot-patch --features "bevy/hotpatching"`, then compare the result with `WGPU_BACKEND=dx12`. Trace the Windows wgpu hotpatching path to identify the source of exit code 0xc0000005; done means hotpatching no longer crashes with the default backend.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- computer-graphics, game-dev, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100