It's because the garbage collector doesn't know about that 30MB of extra memory used by your textures, that it is being accumulated when you are not calling Dispose. All you have to do is call Dispose on your textures when they are no longer needed. It doesn't know when those objects need to be released - you can do a much better job yourself. When it collects them it will finalize them which, like calling Dispose, will release the unmanaged resources.īut the garbage collector cannot 'see' all the unmanaged resources these Texture2D objects are using. Eventually the garbage collector will run, see all these unreferenced Texture2D objects and collect them. What you do need to worry about is the unmanaged resources - in this case the texture memory being used by all these textures you're loading. 99% of the time you don't need to worry about it - the garbage collector is really good at handling managed memory - that's its job!

The memory being used by managed objects will be handled by the garbage collector - in this case each instance of Texture2D uses a tiny bit of managed memory. The important thing to realise is that you're working with both managed and unmanaged resources here. You should use Texture2D.FromFile in Game.LoadContent, and call Dispose in Game.UnloadContent (normally the content manager would handle calling Dispose for you - but because you're not going through the content manager you have to call Dispose yourself). If you really have to load a texture from file and not the content system - you should do this only once for each texture. The 'normal' way to load a texture is to use the content pipeline and the content manager. If it is important, the size of the image is about 10KB.įirst of all you need to understand that what you are doing is pretty strange! I want to make it works like that: load image, release from memory, load image, release from memory and so on, so the program should always takes 95MB (it takes 95MB when image is loaded only once in previous method). I don't understand why it takes this 6MB (101-95). It works like that: first it takes 95MB and then goes slowly to about 101MB (due to the I've found, that if I change the code to: t.Dispose()

Can You explain why (how) it works like that?.

Now, when I run my game, it takes 95MB of RAM and it goes slowly to about 130MB (due to the code I've posted, without this code it remains at 95MB), then goes immediately to about 100MB (garbare colletion?) and again goes slowly to 130MB, then immediately to 100MB and so on.

'Update' method is working like a loop, so this code is called In the 'Update' method of the 'Game' class I have this code: t = Texture2D.FromFile( ) //t is a 'Texture2D t '

Load textures on demand