absulitI've been in a bit of a performance rabbit whole in my #webgpu library POINTS. I didn't realize that switching between demos was creating a lot of references to buffers and textures and other objects. I was able to see this thanks to the WebGPU Inspector by @brendan so now between switches I was able to verify that all items I destroyed really were destroyed.
I gotta say it's really nice to work on performance, and I think #devs in general are never aware of the damage we cause by not looking into it. I'm saying this because I think I've never paid to much attention to it until now and I want to actually make things faster. After this I wanted to take a look at the #JS memory spikes or memory in general, but the memory profilers are just unbearably confusing, too crowded and I don't know where to look
I just want to know if my functions and variables are causing a memory spike, what the fuck is this! (see image for reference)
