Skip to content

fix(wgpu): skip zero-area surfaces; render through D3D12 or GL on Windows - #2

Merged
unohee merged 2 commits into
mainfrom
fix/wgpu-zero-area-surface
Oct 30, 2026
Merged

unohee merged 2 commits into
mainfrom
fix/wgpu-zero-area-surface

Conversation

@unohee

@unohee unohee commented Oct 30, 2026

Copy link
Copy Markdown
Contributor

Merges the two commits de-artifact already ships (750ce16, tag pinned/de-artifact-aud2367) into main, so every Intrect consumer sits on one tip before the fork moves into the intrect-plugin monorepo (framework/egui-baseview). The branch fast-forwards from main; CI on the branch tip is green.

Configuring a surface or creating a texture with a zero dimension is a
wgpu validation error, and wgpu's default handler panics on it inside
baseview's frame/event callback, where a plug-in host aborts. Hosts can
collapse an embedded view to 0x0. Measured with de-artifact on a Windows
10 VM: SetWindowPos(editor child, 0x0) -> 'Both Surface width and height
must be non-zero' -> exit 0xC0000409 (AUD-2367).
wgpu enumerates Vulkan before D3D12 and keeps that order between
adapters of the same type, so a normal Windows GPU rendered the editor
through Vulkan and pulled every Vulkan implicit layer (overlays, capture
and vendor layers) into the plug-in host's process. D3D12 drives the
same GPUs and its WARP adapter covers machines with no GPU driver; GL
remains for GPUs without a D3D12 driver. WGPU_BACKEND still overrides
the default for diagnosis (de-artifact AUD-2367).
@unohee
unohee merged commit e6bbbd1 into main Oct 30, 2026
9 checks passed
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