You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
When hello-triangle starts up under wasm, it configures the surface with window.inner_size(), but that size is zero. Furthermore, the WebGPU backend does not catch this validation error.
The example should not configure with zero size. (Is this a winit bug that the canvas size is incorrectly reported?)
This should be a validation error on all backends, or succeed on all backends. Instead, on WebGPU this does not produce a wgpu validation error, but produces a validation error from the underlying WebGPU, and rendering then succeeds later.
The texture size ([Extent3D width:0, height:0, depthOrArrayLayers:1]) or mipLevelCount (1) is empty.
at ValidateTextureDescriptor (../../third_party/dawn/src/dawn/native/Texture.cpp:478)
On WebGL it panics with a validation error inside wgpu.
Description
When
hello-triangle
starts up under wasm, it configures the surface withwindow.inner_size()
, but that size is zero. Furthermore, the WebGPU backend does not catch this validation error.Repro steps
cargo xtask run-wasm --bin hello-triangle
cargo xtask run-wasm --bin hello-triangle --features webgl
Expected vs observed behavior
The example should not configure with zero size. (Is this a winit bug that the canvas size is incorrectly reported?)
This should be a validation error on all backends, or succeed on all backends. Instead, on WebGPU this does not produce a wgpu validation error, but produces a validation error from the underlying WebGPU, and rendering then succeeds later.
On WebGL it panics with a validation error inside wgpu.
Platform
x86_64-apple-darwin
The text was updated successfully, but these errors were encountered: