You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
The text was updated successfully, but these errors were encountered:
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
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 thedestroy
methods is to ensure resources can predictably be deallocated even in garbage collected environments (such the web).The text was updated successfully, but these errors were encountered: