Does GPUBuffer.destroy() guarantee immediate resource reclamation across browser vendors?
Resource Lifecycle Management in WebGPU WebGPU employs an explicit memory model where GPUBuffer and GPUTexture objects are managed by the application. To prevent memory leaks, the destroy() method is provided to explicitly signal that the resource is no longer needed, bypassing the standard garbage collection cycle. While the specification defines the intent
webgpu