Jump to content
  • Advertisement
Sign in to follow this  
smally

Memory leak

This topic is 3787 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

I think it's about time I learnt how exactly to read the output for a memory leak in VisualStudio 2005 (using C++) I'm usually quite neat, or my memory leak is an obvious one, but I am having trouble finding this one, and was hoping someone would describe what exactly the output text is trying to say to me:
Dumping objects ->
{156} normal block at 0x00665AC8, 4 bytes long.
 Data: <$qI > 24 71 49 00 
Object dump complete.

Share this post


Link to post
Share on other sites
Advertisement
Quote:
{156} normal block at 0x00665AC8, 4 bytes long.

At allocation id ({156})
with the memory address (normal block at 0x00665AC8)
the size of the type leaked is ( 4 bytes long.)
The contents of the leaked 4 bytes leaked are 24 71 49 00

Share this post


Link to post
Share on other sites
If you want to see where the leak was generated you can use _CrtSetBreakAlloc(156) to break on the allocation.

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.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!