Skip to content

Asynchronously get ShaderModule creation result and compilation info - #25352

Open
beicause wants to merge 10 commits into
bevyengine:mainfrom
beicause:async-shader-load
Open

Asynchronously get ShaderModule creation result and compilation info#25352
beicause wants to merge 10 commits into
bevyengine:mainfrom
beicause:async-shader-load

Conversation

@beicause

@beicause beicause commented Aug 10, 2026

Copy link
Copy Markdown
Member

Objective

Fixes #25342

Solution

Refactor ShaderCache to make it only holds processed shader source instead of wgpu::ShaderModule and make load_module async.

Testing

Tested shader_material with an invalid shader on native with file_watcher hot-reloading and on web.

Note: blocked by gfx-rs/wgpu#10039. Currently panics on webgpu due to wgpu popErrorScope bug.

@JaySpruce JaySpruce added C-Bug An unexpected or incorrect behavior A-Rendering Drawing game state to the screen O-Web Specific to web (WASM) builds S-Needs-Review Needs reviewer attention (from anyone!) to move forward D-Async Deals with asynchronous abstractions labels Aug 10, 2026
@github-project-automation github-project-automation Bot moved this to Needs SME Triage in Rendering Aug 10, 2026
@beicause beicause added the S-Blocked This cannot move forward until something else changes label Aug 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-Rendering Drawing game state to the screen C-Bug An unexpected or incorrect behavior D-Async Deals with asynchronous abstractions O-Web Specific to web (WASM) builds S-Blocked This cannot move forward until something else changes S-Needs-Review Needs reviewer attention (from anyone!) to move forward

Projects

Status: Needs SME Triage

Development

Successfully merging this pull request may close these issues.

ShaderModule creation error isn't handled on web

2 participants