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

Dependencies between resources prevent destroy from doing its job #4787

Closed
nical opened this issue Nov 27, 2023 · 1 comment
Closed

Dependencies between resources prevent destroy from doing its job #4787

nical opened this issue Nov 27, 2023 · 1 comment
Labels
type: enhancement New feature or request

Comments

@nical
Copy link
Contributor

nical commented Nov 27, 2023

We currently don't deallocate resources as long as their reference count (as in the counter in the Arc itself) does not get down to a certain number which is semantically equivalent to zero (See the checks).

Dependencies between resources, for example a texture view holding on to a texture, contribute a strong reference count, however we need texture.destroy to be able to deallocate textures even while it is referenced by texture views. This is important because the role of the destroy methods is to ensure resources can predictably be deallocated even in garbage collected environments (such the web).

@nical nical changed the title Dependecies between resources prevent destroy from doing its job Dependencies between resources prevent destroy from doing its job Nov 27, 2023
@teoxoy teoxoy added the type: enhancement New feature or request label Nov 27, 2023
@teoxoy teoxoy added this to the WebGPU Specification V1 milestone Nov 27, 2023
@nical
Copy link
Contributor Author

nical commented Dec 12, 2023

TODO

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement New feature or request
Projects
Status: Done
Development

No branches or pull requests

2 participants