How to Simply Manage Texture Release?

[gameatp]

Texture will take up a lot of memory, so I want to manage it in a simple and effective way.

I found that texture has such a function in playcanvas

But this destroy method I checked that the following material destroy was not invoked, that is to say, this method needs to be called manually, but I released if there are references that will lead to errors, I want to know if there is a simple and good way to deal with it.
I think the engine should add a reference count to the texture?

[yaustar]

Looks like asset.unload should release the VRAM used by the texture and you can use asset.loaded to check if the resource has been loaded.

Links:

Unloading asset in code

Hello, I am trying to unload asset to save memory after I load and then use it. It seems like assets are cached forever even after asset.unload() - after asset.unload() I called pc.app.assets.loadFromUrl(url, ‘model’, function() { // never get here because the asset is cached (exists in the asset repository ) I guess }); I know I can use pc.app.assets.getByUrl(url) to reuse one in the repository, but, I do not want to keep the asset in memory every time I load it - I want to load a model a…

https://developer.playcanvas.com/en/api/pc.Asset.html#loaded
https://developer.playcanvas.com/en/api/pc.Asset.html#unload

[gameatp]

If the texture asset is used in the material of another model, calling unload will cause an error.
I think this problem is more troublesome, maybe we have to count the resource references, and unload can be invoked only if it is not used.