bevyengine / bevyengine/bevy

Chrome error "Unable to find a GPU"; vkcube working normally.

Open
#9,273 3 comments 1 reaction 0 assignees View on GitHub
A-Rendering C-Bug C-Examples O-Linux O-Web O-WebGPU
Dominant language
Rust
Stars
48.2k
Forks
4.8k
Avg merge
3d 16h
Merged PRs (30d)
171

Description

## Bevy version

Not sure, I am getting this error online while trying the WebGPU examples at
https://bevyengine.org/examples-webgpu/2D%20Rendering/2d-gizmos/

## Relevant system information

Chrome Version 115.0.5790.102 (Official Build) (64-bit)
5.10.186-2-MANJARO
Desktop: GNOME v: 44.3 tk: GTK v: 3.24.38 wm: gnome-shell dm: GDM v: 44.1
Wayland
GPU Intel TigerLake-LP GT2 [Iris Xe Graphics]

## What you did

Open the example at the link above.

## What went wrong

See loader, but no output. Get 2 errors in the web console.

errors
panicked at 'Unable to find a GPU! Make sure you have installed required drivers!', crates/bevy_render/src/renderer/mod.rs:130:10

Stack:

Error
at imports.wbg.__wbg_new_abda76e883ba8a5f (https://bevy-webgpu-examples.pages.dev/2D%20Rendering/2d-gizmos/wasm_example.js:413:21)
at wasm://wasm/03e0e176:wasm-function[28254]:0xbf5ff8
at wasm://wasm/03e0e176:wasm-function[9853]:0xa0322e
at wasm://wasm/03e0e176:wasm-function[19137]:0xb753db
at wasm://wasm/03e0e176:wasm-function[30650]:0xc4c7a0
at wasm://wasm/03e0e176:wasm-function[16646]:0xb1a537
at wasm://wasm/03e0e176:wasm-function[385]:0x1d1940
at wasm://wasm/03e0e176:wasm-function[6585]:0x88936e
at wasm://wasm/03e0e176:wasm-function[31109]:0xc7a7e7
at wasm://wasm/03e0e176:wasm-function[20613]:0xb959b6

Uncaught (in promise) RuntimeError: unreachable
at 03e0e176:0xa03254
at 03e0e176:0xb753db
at 03e0e176:0xc4c7a0
at 03e0e176:0xb1a537
at 03e0e176:0x1d1940
at 03e0e176:0x88936e
at 03e0e176:0xc7a7e7
at 03e0e176:0xb959b6
at __wbg_adapter_65 (wasm_example.js:238:10)
at real (wasm_example.js:203:20)

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the 2D gizmos WebGPU example in Chrome 115 on the listed Wayland and Intel GPU system, then inspect the browser console. Trace the panic at crates/bevy_render/src/renderer/mod.rs:130:10 and compare the result with vkcube. Done means the cause is identified and a verified fix or supported workaround is documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust, wasm
Domain
computer-graphics, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.