-
Notifications
You must be signed in to change notification settings - Fork 373
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
Labels
Comments
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
added a commit
that referenced
this issue
Feb 20, 2023
Wumpf
added a commit
that referenced
this issue
Feb 20, 2023
3 tasks
Wumpf
added a commit
that referenced
this issue
Feb 20, 2023
Wumpf
added a commit
that referenced
this issue
Feb 20, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
The text was updated successfully, but these errors were encountered: