ITS THE GRAPHICS :(

Question

Okay, so the "memory leak" I thought I had was being caused by the graphics being used on buttons and backgrounds. Why is this happening?

Vulpes · Answer

Are these graphics produced by something you're doing yourself or by the components you're using? If it's the former, I'd make sure you call Dispose() when you've finished with any Image or Bitmap objects you're loading or creating. If it's the latter, I'd check the documentation to see whether there's something you're not doing which you should be doing to dispose of resources when they're no longer needed.

Sam Hobbs · Answer

Well at least you have learned. In the future you will know how to manage graphics objects better. I think that "graphics we created" does not answer the question. Were they created during execution of the program or created separately and then loaded and used by the program? Alternatively to calling Dispose, if it is possible to create the object once and use the same object many times then that would be the most efficient. The next best solution is to do as suggested already; create an object then dispose of it later. I assume you were creating the object many times but not disposing. So one possibility is to add a dispose as suggested but another possibility is to move the location where the object creation occurs.

patrick · Answer

As painful as it is, disposing of every graphic seems to solve the issue, I got and used the memory flush from http://codesmithdotnet.blogspot.com/2008/02/release-memory-in-windows-form.html as a shortcut.

patrick · Answer

Well they are graphics we created and put as background images using the properties window on the designer in visual studio.

ITS THE GRAPHICS :(

Answers (4)