about the Destory() function

Unity Engine
1

in some cases i have use www to download many texture2d objects,

after these texture object are not useful or referenced anymore, should i

manually call Object.Destory() to release the memory?

thx!

2

No i don’t think so, it should not affect performance (Pay attention to “I think”)

3

thx sturestone

since the existence of the Object.FindObjectOfType function, the unity engine may keeps all the references of the created Objects, so i am wondering if i need to tell the engine to erase the references

4

You don’t have to worry about memory management; Unity takes care of that. The garbage collector will clean up unused stuff when necessary.

–Eric

5

unless you’re using WWW.Texture. If you assign some variable = WWW.Texture that does not get garbage collected, even after the object you assigned the texture to is destroyed. I had to write my own garbage collection routine to clean up after that.

6

Sounds strange… I thought mono/unity will take care of the reference count properly.

7

So did I, but that is one of the two major memory related issues that we discovered with our project early on. The other one was that each call to WWW.Texture creates a new texture instance, so if you want to apply the same texture to multiple objects without using more memory you need to manually create an instance of the texture, then assign that instance to the objects.

Fixing those two things let us reduce our memory consumption by about tenfold (about 90% of our texture assets are dynamically loaded)