Sign in to follow this  

D3D9 memory still allocated

Recommended Posts

Direct3D9: (INFO) :MemFini!
Direct3D9: (ERROR) :Memory still allocated!  Alloc count = 143
Direct3D9: (ERROR) :Current Process (pid) = 000010b4


Direct3D9: (ERROR) :Total Memory Unfreed From Current Process = 2083940 bytes
Direct3D9: :====> EXIT: DLLMAIN(61d4d9a0): Process Detach 000010b4


I use these direct x objects, all of which I am sure I release() and set to NULL;





map<wstring, LPDIRECT3DTEXTURE9>


PIX shows that the index and vertex buffer, created by the application, are never destroyed (I call release on both). It also shows that two d3d9 surfaces, created by direct3d, are never destroyed (usages: rendertarget and depthstencil).


When I call release() on the graphics device there is still a reference to it, so calling release on it again leaves no leaks. I doubt this is the solution, just doesn't seem right. What other methods would add a reference to the device? Or what could it be that I am missing? Thank you.



Share this post

Link to post
Share on other sites

I find that DX9 memory memory leaks are really hard to track down. I had a similar number of leaks which I tracked down to just a couple of issues in my code (I hadn't freed a  pixel shader object and a vertex declaration). But failing to release just a couple of objects means that directx itself doesn't shutdown properly which means that any bound textures and shaders aren't released either.


I suspect that it isn't ordering, but just some object that you've missed somehow. Working out which of your 143 leaks is the real problem versus which are just side effects of your leak is tricky.

Share this post

Link to post
Share on other sites

Thanks. My problem was that I called D3DXCreateFont twice for the same object. A small, sneaky line created it the second time. The debug output was irrelevant in this case. The PIX object list output was also distracting. What worked best in this situation and probably will in most direct3d leak errors is to use PIX's  "log of all D3D calls made in frame number:" on frame one.

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this