Skip to content
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

use texture/buffer destroy in resource pool #592

Closed
Wumpf opened this issue Dec 18, 2022 · 0 comments · Fixed by #1359
Closed

use texture/buffer destroy in resource pool #592

Wumpf opened this issue Dec 18, 2022 · 0 comments · Fixed by #1359
Assignees
Labels
enhancement New feature or request 🔺 re_renderer affects re_renderer itself

Comments

@Wumpf
Copy link
Member

Wumpf commented Dec 18, 2022

seems to be a fairly recent addition to WebGPU spec that I wasn't aware of: Textures & Buffers can be explicitly destroyed now! We should use that in our resource pools as we have all the information we need.

https://www.w3.org/TR/webgpu/#dom-gputexture-destroy
https://www.w3.org/TR/webgpu/#dom-gpubuffer-destroy

@Wumpf Wumpf added the 🔺 re_renderer affects re_renderer itself label Dec 18, 2022
@Wumpf Wumpf self-assigned this Dec 18, 2022
Wumpf added a commit that referenced this issue Dec 18, 2022
add resource destruction callback
Fixes #592
Wumpf added a commit that referenced this issue Dec 18, 2022
add resource destruction callback
Fixes #592
Wumpf added a commit that referenced this issue Dec 18, 2022
add resource destruction callback
Fixes #592
Wumpf added a commit that referenced this issue Dec 18, 2022
add resource destruction callback
Fixes #592
Wumpf added a commit that referenced this issue Dec 18, 2022
add resource destruction callback
Fixes #592
@Wumpf Wumpf added the enhancement New feature or request label Dec 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request 🔺 re_renderer affects re_renderer itself
Projects
None yet
1 participant