-
Notifications
You must be signed in to change notification settings - Fork 51
Issues: Traverse-Research/gpu-allocator
⚠️ NOTICE for
metal
users on gpu-allocator 0.26
⚠️
#224
by MarijnS95
was closed Oct 3, 2024
Closed
4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Vulkan visualizer's
render_memory_block_window
calls render_breakdown_ui
#238
opened Jul 7, 2024 by
h3r2tic
Split out the visualizers to a separate application
roadmap
#203
opened Feb 5, 2024 by
Jasper-Bekkers
Size of fully vendored
gpu-allocator
with "d3d12"
is quite large
#181
opened Oct 3, 2023 by
jimblandy
Visualizer UI subtract with underflow
bug
Something isn't working
rust
Pull requests that update Rust code
#147
opened Dec 13, 2022 by
janie177
Vulkan allocator should determine limits based off what the user passes in, not what Vulkan reports
#126
opened Aug 26, 2022 by
i509VCB
Vulkan allocator should respect the
maxMemoryAllocationCount
limit
#125
opened Aug 26, 2022 by
i509VCB
No way to manually destroy memory blocks before Device is destroyed
#96
opened Jan 26, 2022 by
Grimeh
It's impossible to bind to a host memory which is not coherent.
#85
opened Dec 14, 2021 by
nikitablack
'There is a memory type that is host visible, but not host coherent.' warning on MacOS
#84
opened Dec 1, 2021 by
expenses
Add option for different color per allocation in visualizer.
enhancement
New feature or request
good first issue
Good for newcomers
#58
opened Sep 7, 2021 by
manon-traverse
ProTip!
Find all open issues with in progress development work with linked:pr.