Initial memory visualizer for Vulkan

Traverse-Research / gpu-allocator

🦀 GPU memory allocator for Vulkan, DirectX 12 and Metal. Written in pure Rust

https://traverse.nl/

Apache License 2.0

373 stars 49 forks source link

Initial memory visualizer for Vulkan #128

Closed Jasper-Bekkers closed 2 years ago

Jasper-Bekkers commented 2 years ago

This actually does two things;

It has an optimization for the callstack resolution which now only happens when it needs to instead of eagerly doing it all the time. This saves significant time in dbghelp.dll and saves some memory too since we only need to store the stack pointers instead of the string
It includes a new allocation overview window that is just a flat list of all allocations that are currently being held by the allocator, including their name. This makes it super easy to track down where memory is being wasted.

Jasper-Bekkers commented 2 years ago

@MarijnS95 I restored the branch because this was causing internal build failures; which is why this repo is set not to delete branches when merging in the first place :-)

MarijnS95 commented 2 years ago

IMHO we should reference the main branch more eagerly after merging, or push a tag for as long as this rev needs to stick around, instead of leaving unused branches cluttering up which we don't have as a workflow anywhere else (and this kind of thing happened before, rev references to branches aren't reliable enough).

(Besides, it's quite tricky to get this right in the GitHub app which still jitters the "Load more items" and "Delete merged branch" button around a lot)

Now that the internal revision is updated, can the branch be re-removed? :pleading_face: