Skip to content

Update wgpu to 26 and wasm-bindgen to 0.2.100#7340

Closed
torokati44 wants to merge 1 commit intoemilk:mainfrom
torokati44:wgpu-26
Closed

Update wgpu to 26 and wasm-bindgen to 0.2.100#7340
torokati44 wants to merge 1 commit intoemilk:mainfrom
torokati44:wgpu-26

Conversation

@torokati44
Copy link
Contributor

  • I have followed the instructions in the PR template

There are new duplicate crates in the dep tree (core-*), but ndk-sys is deduplicated in exchange.

@github-actions
Copy link

Preview available at https://egui-pr-preview.github.io/pr/7340-wgpu-26
Note that it might take a couple seconds for the update to show up after the preview_build workflow has completed.

@dezajno
Copy link

dezajno commented Jul 26, 2025

Is the wgpu version upgrade blocked by something? I'd be interested in pushing this as I need it for an own project. Can I help somehow?

@Kumpelinus
Copy link
Contributor

Currently the issue seems to be that wgpu is now no_std and the macro from the puffin crate still pulls in std components in the expanded macro (like std::sync::OnceLock) which doesn't work with no_std ofc. I will probably take a look at fixing this later today. (The demo app does compile without the profiling/profile-with-puffin feature so that seems to be the only blocker besides the macOS Issues)

@Kumpelinus
Copy link
Contributor

@torokati44 should I open a different PR or should I edit your existing one (If you give me access to the branch)?

@Kumpelinus
Copy link
Contributor

Kumpelinus commented Aug 4, 2025

I’m not sure which crate should host the fix. The underlying issue lies in puffin, which is currently unmaintained, so the patch could land in one of four places:

  • the egui-examples crate the error is happening in (other egui users will likely hit the same problem),
  • the egui crate itself
  • wgpu, or
  • the profiling crate.

@torokati44
Copy link
Contributor Author

@Kumpelinus I think it's easier if you open your own, I won't mind. I don't think this permission can be easily granted to you.

@Kumpelinus
Copy link
Contributor

Ok, will do 👍

@nicoburns
Copy link
Contributor

I think bumping arboard will fix the duplicated core-* dependencies

@torokati44
Copy link
Contributor Author

Are you sure? I wasn't able to do it that way...

@torokati44
Copy link
Contributor Author

Merged as #7540.

@torokati44 torokati44 closed this Sep 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants