[p5.js 2.0+ Bug Report]: Check storage buffer limits when compiling strands shaders #9349

Most appropriate sub-area of p5.js?

• Accessibility
• Color
• Core/Environment/Rendering
• Data
• DOM
• Events
• Image
• IO
• Math
• Typography
• Utilities
• WebGL
• WebGPU
• p5.strands
• Build process
• Unit testing
• Internationalization
• Friendly errors
• Other (specify if possible)

p5.js version

No response

Web browser and version

No response

Operating system

No response

Steps to reproduce this

Description

When strands generates WGSL, it creates a binding for each uniformStorage without keeping count. If a shader uses more storage buffers than the device allows (8 per stage by default), nothing catches it in p5, you just get a WebGPU validation error in the console when the pipeline is created.

It can be easy to hit this without realizing. For example, in a vertex/fragment shader every storage buffer gets declared in both stages, and some devices allow fewer storage buffers in the vertex stage, or none at all. This is particularly problematic on mobile which users tend not to test.

Since the renderer is already available on strandsContext, strands could count the storage bindings per stage while building the shader and compare them against device.limits. If a shader goes over, it could throw a friendly error that says how many buffers it uses, what the limit is, and which uniforms are involved, etc.