Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Validation limits are too high #5296

Closed
munrocket opened this issue Feb 23, 2024 · 5 comments
Closed

Validation limits are too high #5296

munrocket opened this issue Feb 23, 2024 · 5 comments

Comments

@munrocket
Copy link
Contributor

munrocket commented Feb 23, 2024 •
edited
Loading

I have integrated gpu card on one PC and all examples gives this error

webgpu.js:331 panicked at 'Unable to find a suitable GPU adapter!: RequestDeviceError { inner: WebGpu(JsValue(OperationError: Required limit (255) is greater than the supported limit (0).
 - While validating maxVertexBufferArrayStride
 - While validating required limits

This limit probably required only for one example.
@munrocket munrocket changed the title Hello compute example not working Validation limits are too high Feb 23, 2024
@cwfitzgerald cwfitzgerald transferred this issue from gfx-rs/wgpu-rs.github.io Feb 23, 2024
@cwfitzgerald
Copy link
Member

Okay this is very weird, as maxVertexBufferArrayStride is required to be at least 2048 - so requesting 255 should be totally fine.

@teoxoy
Copy link
Member

teoxoy commented Feb 26, 2024

Looks like a dawn issue.

@munrocket
Copy link
Contributor Author

munrocket commented Feb 28, 2024 •
edited
Loading

Looks like a dawn issue.

Maybe because I used linux. But other websites was ok. I can check Firefox Nightly.

@munrocket
Copy link
Contributor Author

With C++ (dawn) I can set validation limit to any amount and this error go away.
I suppose with rust+wgpu the same situation?

@alexniver alexniver mentioned this issue Apr 24, 2024
Open
@teoxoy
Copy link
Member

teoxoy commented Jul 3, 2024

I don't think this is an issue on our side, the error in the top most comment looks like a Chromium error that is not spec-compliant.

@teoxoy teoxoy closed this as not planned Won't fix, can't repro, duplicate, stale Jul 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@cwfitzgerald @munrocket @teoxoy