   Finding memory leak with PIX
  I have been trying to figure out how to use PIX for debugging my DirectX applications and have had a lot of trouble (it seems to bear no resembalance to what the documentation says about it), and I'm currently trying to find a memory leak(s) with it. But it seems no matter how I run, it won't give me object information, and more importantly weather an object is alive or dead on the last frame, any ideas?Thanks   
  I've found the memory leak, but it would still be nice to know how to find memory leaks through PIX, I've tired running an experiment with "Statistics from each frame, using counterset" -> Resource_Usage, and that doesn't seem to be working for me.   ;  The only memory leaks that I have been able to detect with PIX are when D3D objects are not destroyed at the end of the application.  In this case, you can take a frame snapshot with F12, then look at the window section titled 'Objects'.  There you can find the list of all API objects, which frame they were created in, and more importantly for you, which frame they were destroyed in.  If it says never in that column, then you know which object to go looking for in your code.Don't give up on PIX just yet - it really is a useful tool!   ;  I wonder: why are you not using the debug runtimes for finding memory leaks? I mean, PIX is a great tool, but using it for finding memory leaks seems a bit of too much work.   ;  Yeah I don't think I've ever used PIX to find memory leaks, I didn't even know it was designed to that.  Typically I use PIX for tracking performance, debugging shaders, and looking at vertex buffer or texture data.   ;  Ok, thanks for the advise =]   