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.

Sign up for GitHub

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

Jump to bottom

Device.tick with new mach Core backends #1288

Closed

emidoots opened this issue Oct 21, 2024 · 0 comments · Fixed by #1289

Labels

bug

Member

emidoots commented Oct 21, 2024

After removing GLFW, with the new pure-Zig mach Core backends, we need to invoke Device.tick() somewhere:

This issue might be related to a number of issues on the tracker.

Summary
For any given sysgpu backend (DX12, Vulcan, etc. etc.), Device.tick is not called.
which means processQueuedOperations is never called and device.submit_objects is never cleared.
it is called in deviceTick, but that is not called either.
Calling Device.tick in an example's tick method fixes the memory leak.

Possibly related issues:
#1232
#1252 (Pretty sure this issue is the same)
#1253
#1259 (I think commands are added to the queue as submit objects, and never end up getting sent)
#1270
#1271
#1275

emidoots added the bug label

RonaldZielaznicki mentioned this issue

Call sysgpu device tick #1289

Merged

1 task

emidoots closed this as completed in #1289

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment