This is as funny as it is interesting so I thought I'd let you all take a look. I'm currently developing a 2D engine as part of a small 3D engine project, the 2D interface uses DirectX9 textured quads to display graphics. (If anyone happens to be interested).
Anyway I started setting up the animation functions for the sprite class. In short I made a terrible mistake, rather than load the textures into video ram before hand, then change them each frame, the program instead loaded them into ram every frame. That's about 25kb of memory lost, sixty times a second.
I submit to you evidence of this programmers worst nightmare, oh mighty task manager show me why my framerate is dropping!

P.S. Apologies for the file name, at the time it was the only thing I could think!

You may notice the permanently leaked 2GB :p

9 Years
Discussion Span
Last Post by DarthPJB

I guess its time for you to toss what you've done into the bit bucket and do it again the right way.

Well I've re-written the function and tweaked the class and it actually switches texture-memory addresses to animation 'backbuffers' now, thus no leakage! However I still thought it worthy of note :p

This topic has been dead for over six months. Start a new discussion instead.
Have something to contribute to this discussion? Please be thoughtful, detailed and courteous, and be sure to adhere to our posting rules.