Skip to content

fix(engine): verify WebGPU device creation before capture - #6343

Open
user-github-me wants to merge 1 commit into
heygen-com:mainfrom
user-github-me:fix/webgpu-device-gate
Open

user-github-me wants to merge 1 commit into
heygen-com:mainfrom
user-github-me:fix/webgpu-device-gate

Conversation

@user-github-me

Copy link
Copy Markdown
Contributor

An available WebGPU adapter can still reject device creation. For compositions declaring data-requires-webgpu, capture now checks that a temporary device can be created. Adapter and device requests share a ten-second deadline, and every created probe device is destroyed, including late completions.

This completes the accepted device-check remainder of #5775, following the Windows DXC launch fix in #5830. The existing software-WebGPU policy still applies. The probe uses default device requirements; compositions request their own renderer-specific features and limits.

Validation: seven targeted regressions fail on the original source. The four focused engine suites pass 128 tests with one existing Linux-only skip on macOS. Full build, engine typecheck, lint/format, test reachability, normal commit hooks, comment checks and Mint documentation checks pass. Native Chrome 152 on macOS passes hardware device creation/cleanup and controlled device-rejection checks; the Windows DLL failure was not reproduced locally.

Fixes #5775

@mintlify

mintlify Bot commented Oct 25, 2026

Copy link
Copy Markdown

Preview approval required

This pull request comes from a fork, so Mintlify won't build a preview until someone with write access approves commit ae89ad5.

Approve preview

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

1 participant