Skip to content

chore(deps): wgpu 30.0.2 - #163

Merged
with-developer merged 1 commit into
mainfrom
chore/wgpu-30.0.2
Nov 16, 2026
Merged

with-developer merged 1 commit into
mainfrom
chore/wgpu-30.0.2

Conversation

@with-developer

@with-developer with-developer commented Nov 16, 2026 •

Copy link
Copy Markdown
Owner

Purpose

wgpu 30.0.2 (2026-11-12) is a patch release of the whole wgpu family. Its fixes include a use after free of a mapped buffer when a device is lost or destroyed, a texture id leak when a surface acquire returns no texture, and explicit Send and Sync for wgpu-core.

Changes

Cargo.lock only: wgpu, wgpu-core, wgpu-core-deps-apple, wgpu-core-deps-windows-linux-android, wgpu-hal, wgpu-types, wgpu-naga-bridge, naga and naga-types, 30.0.1 to 30.0.2. The manifest's "30" already allows it, so no source file changes. Nothing changes for a client of the libraries.

Testing

  • cargo fmt --check, cargo clippy --workspace --all-targets --locked -- -D warnings and cargo test --workspace --locked pass; cargo +1.87 check --workspace --all-targets --locked passes.
  • The Mac library of the XCFramework builds, and scripts/bench_app_on_mac.sh -autorun passes with its three checks.
  • Decoding into planes, emberwave-cli bench on the 1080p and 4K scene streams, built with the old and the new lock file, alternated, three rounds of 600 frames. Mean ms per frame, lowest to highest of the rounds: 1080p 0.35 to 0.39 old and 0.36 to 0.39 new; 4K 0.83 to 0.85 old and 0.84 new. GPU time per frame the same, 0.12 to 0.13 ms at 1080p and 0.51 ms at 4K. The Mac was not quiet (load average 35 to 55), so the runs say no regression, not an improvement.

The tests that read wgpu's internal counters read the buffer, buffer memory and texture memory counters, not the texture count that 30.0.1's Vulkan backend did not increment on creation; they pass.

A patch release of the whole wgpu family (wgpu, wgpu-core, wgpu-hal,
wgpu-types, naga and their helper crates), lock file only: the manifest's
"30" already allows it. Its fixes include a use after free of a mapped
buffer when a device is lost or destroyed, a texture id leak when a surface
acquire returns no texture, and explicit Send and Sync for wgpu-core.

Checked: fmt, clippy -D warnings, cargo test --workspace, cargo check on
Rust 1.87, the Mac library of the XCFramework and the benchmark app's
-autorun. Decoding into planes with emberwave-cli bench, old lock file
against new, alternated, three rounds of 600 frames: 1080p 0.35 to 0.39 ms
and 0.36 to 0.39 ms, 4K 0.83 to 0.85 ms and 0.84 ms, GPU time unchanged,
within the runs' spread (the Mac's load average was 35 to 55).

Claude-Session: https://claude.ai/code/session_019fJGoCTvP5e7n599q3ZQ42
@with-developer
with-developer merged commit 9407637 into main Nov 16, 2026
7 checks passed
@with-developer
with-developer deleted the chore/wgpu-30.0.2 branch November 16, 2026 09:36
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.

1 participant