step025 leaking memory in wgpuSurfaceGetCurrentTexture with wgpu-native?

[meesvermeulen]

When I run the example code from step025 compiled with GCC with the address sanitizer enabled, with the wgpu-native backend, it reports many direct leaks of objects allocated from the function wgpuSurfaceGetCurrentTexture. In commit ba57c81 the wgpuTextureRelease function is specifically not called on the surface texture for wgpu-native backends. When I do call it, the application crashes indeed. Am I missing something? Is this a bug in wgpu-native?

[eliemichel]

Thanks for reporting! I was indeed not happy with this #ifdef that skips releasing at the time, it is (or was?) probably a bug of wgpu-native. We should test with latest version, but I'll wait before v1 of webgpu.h is released (as it's coming soon, lots of breaking changes in the API lately). Keeping this open to remin me about it!

[Waffle1434]

+1, this becomes a lot more apparent when changing the surface's present mode from PresentMode::Fifo (vsync) to PresentMode::Immediate (uncapped). I'm leaking about 1MB per 5 seconds when running at ~3000fps, and it will grow in hundreds of megabytes.

[Waffle1434]

Resolution: #51