Menu

1 / 5

WebGPU fails silently: buffer limits, a missing COPY_SRC and default requiredLimits

DEV Community: typescript·Rodion Kazennov·12 days ago
#Q2yNa9V2
#devtotypescript#devto#dev#buffer#every
Reading 0:00
15s threshold

The run finished at 0.04 ms per step, roughly 500 times faster than the simulation should have run at that size. The health report was clean: no NaN, no infinity, the largest force was zero, and every particle had zero neighbours. It was clean because nothing had been computed.

This happened in protocell-genesis , a WebGPU simulation I built to test whether a coarse-grained "primordial soup" can assemble itself into a closed vesicle, a bilayer membrane with water trapped inside. In this model it can't, and the repository has the measured reasons. The largest run had 483,268 particles. Over the project, six bugs behaved like the one above: no exception, no error on the page, and numbers that looked plausible or even good. Three of them are specific to WebGPU. Here they are, with what each one looked like and what changed.

1. A buffer larger than the device allows

At a box size of 85 σ the Verlet neighbour list needed 5,484,474,528 bytes.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.