Open Bug 1841898 Opened 2 years ago Updated 1 year ago

Specialize validation error messages in cases where the adapter would support e.g. an allocation but device creation didn't request a high enough limit

Categories

(Core :: Graphics: WebGPU, enhancement, P3)

Product:
Core
Component:
Graphics: WebGPU
Type:
enhancement

Tracking

()

People

(Reporter: jgilbert, Unassigned)

References

(Blocks 2 open bugs)

Details

Just an idea!

I feel like we've seen this pattern multiple times from newer authors, for example:

  • Author: I'm seeing an inconsistency in the value of the maxBufferSize limit. The adapter and device value don't agree with each other.
  • Helper: Are you requesting the higher limit in requestDevice? WebGPU always enforces the default limits unless you explicitly request higher
  • Author: Oh! Oops I'll do that.

This is also a class of error that we might sometimes run into when debugging bug reports of a not-quite-portable app.

Blocks: webgpu-phase-2
No longer depends on: webgpu-v1
Blocks: webgpu-triage
You need to log in before you can comment on or make changes to this bug.