wgpu: DEVICE_REMOVAL_PROCESS_AT_FAULT because DXGI_ERROR_DEVICE_HUNG on W10 with HD 4600

Description Hi, I’m getting this error when running Bevy’s breakout demo. A window shows up for a second or two, then disappears. I assume the error is something to do with wgpu, since most of the output seems to originate from it.

PS C:\Users\sdasda7777\Desktop\bevy> cargo run --example breakout
    Finished dev [unoptimized + debuginfo] target(s) in 8.11s
     Running `target\debug\examples\breakout.exe`
2023-08-06T11:04:54.926997Z  INFO bevy_winit::system: Creating new window "Bevy App" (0v0)
2023-08-06T11:04:55.436293Z  INFO bevy_render::renderer: AdapterInfo { name: "Intel(R) HD Graphics 4600", vendor: 32902, device: 1042, device_type: IntegratedGpu, driver: "", driver_info: "", backend: Dx12 }
2023-08-06T11:04:56.280757Z  INFO bevy_diagnostic::system_information_diagnostics_plugin::internal: SystemInfo { os: "Windows 10 Pro", kernel: "19045", cpu: "Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz", core_count: "4", memory: "27.9 GiB" }
2023-08-06T11:04:57.845688Z ERROR wgpu_hal::auxil::dxgi::exception: ID3D12Device::RemoveDevice: Device removal has been triggered for the following reason (DXGI_ERROR_DEVICE_HUNG: The Device took an unreasonable amount of time to execute its commands, or the hardware crashed/hung. As a result, the TDR (Timeout Detection and Recovery) mechanism has been triggered. The current Device Context was executing commands when the hang occurred. The application may want to respawn and fallback to less aggressive use of the display hardware). [ EXECUTION ERROR #232: DEVICE_REMOVAL_PROCESS_AT_FAULT]
2023-08-06T11:04:57.848850Z ERROR wgpu_hal::auxil::dxgi::result: Buffer creation failed: 0x887A0005
2023-08-06T11:04:57.849126Z ERROR wgpu::backend::direct: Handling wgpu errors as fatal by default
2023-08-06T11:04:57.849617Z ERROR wgpu_hal::auxil::dxgi::result: Buffer creation failed: 0x887A0005
thread 'Compute Task Pool (1)' panicked at 'wgpu error: Validation Error

Caused by:
    In Queue::write_buffer
    Parent device is lost

', C:\Users\sdasda7777\.cargo\registry\src\index.crates.io-6f17d22bba15001f\wgpu-0.16.3\src\backend\direct.rs:3019:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Encountered a panic in system `bevy_render::globals::prepare_globals_buffer`!
2023-08-06T11:04:57.855172Z ERROR wgpu_hal::auxil::dxgi::result: Buffer creation failed: 0x887A0005
2023-08-06T11:04:57.855323Z ERROR wgpu::backend::direct: Handling wgpu errors as fatal by default
thread 'Compute Task Pool (0)' panicked at 'wgpu error: Validation Error

Caused by:
    In Queue::write_buffer
    Parent device is lost

', C:\Users\sdasda7777\.cargo\registry\src\index.crates.io-6f17d22bba15001f\wgpu-0.16.3\src\backend\direct.rs:3019:5
Encountered a panic in system `bevy_pbr::render::mesh::prepare_skinned_meshes`!
2023-08-06T11:04:57.859215Z ERROR wgpu::backend::direct: Handling wgpu errors as fatal by default
2023-08-06T11:04:57.860080Z ERROR wgpu_hal::auxil::dxgi::result: Buffer creation failed: 0x887A0005
thread 'Compute Task Pool (1)' panicked at 'wgpu error: Validation Error

Caused by:
    In Queue::write_buffer
    Parent device is lost

', C:\Users\sdasda7777\.cargo\registry\src\index.crates.io-6f17d22bba15001f\wgpu-0.16.3\src\backend\direct.rs:3019:5
Encountered a panic in system `bevy_ui::render::prepare_uinodes`!
2023-08-06T11:04:57.863386Z ERROR wgpu::backend::direct: Handling wgpu errors as fatal by default
2023-08-06T11:04:57.864081Z ERROR wgpu_hal::auxil::dxgi::result: Buffer creation failed: 0x887A0005
thread 'Compute Task Pool (0)' panicked at 'wgpu error: Validation Error

Caused by:
    In Queue::write_buffer
    Parent device is lost

', C:\Users\sdasda7777\.cargo\registry\src\index.crates.io-6f17d22bba15001f\wgpu-0.16.3\src\backend\direct.rs:3019:5
Encountered a panic in system `bevy_pbr::render::fog::prepare_fog`!
2023-08-06T11:04:57.866532Z ERROR wgpu::backend::direct: Handling wgpu errors as fatal by default
thread 'Compute Task Pool (1)' panicked at 'wgpu error: Validation Error

Caused by:
    In Queue::write_buffer
    Parent device is lost

', C:\Users\sdasda7777\.cargo\registry\src\index.crates.io-6f17d22bba15001f\wgpu-0.16.3\src\backend\direct.rs:3019:5
Encountered a panic in system `bevy_render::extract_component::prepare_uniform_components<bevy_sprite::mesh2d::mesh::Mesh2dUniform>`!
thread 'Compute Task Pool (1)' panicked at 'called `Result::unwrap()` on an `Err` value: RecvError', crates\bevy_render\src\pipelined_rendering.rs:135:45
error: process didn't exit successfully: `target\debug\examples\breakout.exe` (exit code: 101)

Repro steps I ran the cargo run command on the latest branch of Bevy. I assume either my hardware isn’t supported, or perhaps it’s some software not being present on my computer.

Expected vs observed behavior I’m mainly just unsure what is the issue. Could you clarify whether it’s that my GPU is unsupported, or it’s just a bug? The error isn’t very clear about what the case is 😅

Platform Windows 10, wgpu seems to be v0.16.3