Jump to content
  • Advertisement
Sign in to follow this  

memory leaks

This topic is 3884 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Hi, I am writing the mesh loading using traditional direct x mesh loading function. I also wrote the destructor while deleting the gemoetry also release textures and so on.. It seems to be alright when I debug in normal mode. But when I set the debugging level to more and check validate debugging in the direct x control panel, I found that there still have many memory leaks. Does anyone know about this problem.... Help me...

Share this post


Link to post
Share on other sites
Advertisement
In start menu, click on run option and write: dxcpl
On Direct3D 9 tab you'll find "Break on AllocId" write in it id of your unreleased object and when the program breaks in debug mode, it will break when you create your directx object that is later unreleased when programs exit.

Then you will know what you need to release...

Share this post


Link to post
Share on other sites
The only way you can leak something in Direct3D is by messing up the reference count to COM interfaces.

Learn how to use CComPtr<> properly and all of that messy reference count management just goes away...

I discuss use of CComPtr<> in Chapter 1. Introduction of my book.

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

Participate in the game development conversation and more when you create an account on GameDev.net!

Sign me up!