This project has moved and is read-only. For the latest updates, please go here.

leak detector not detecting leaks (VS 2010)

Apr 12, 2011 at 2:02 PM
Edited Apr 12, 2011 at 2:03 PM

I'm hoping i only need to configure VLD differently, but this is what i run into when i run my project:

 

No memory leaks detected.
Visual Leak Detector is now exiting.
Detected memory leaks!
Dumping objects ->
f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\strcore.cpp(188) : {4876} normal block at 0x14776120, 30 bytes long.
 Data: <T  P            > 54 CD C3 50 0B 00 00 00 0D 00 00 00 01 00 00 00
Object dump complete.

 

What is going on?

Running Win7 x64, compiling and executing in Win32.

Apr 12, 2011 at 4:35 PM

You're not the only one. VLD is showing no leaks, but my VS2010 SP1 is reporting hundreds. I'm running an MDI application, and solely opening and closing our program without officially loading a project/document. Who's right?

No memory leaks detected.
Visual Leak Detector is now exiting.
Detected memory leaks!
Dumping objects ->
f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\dllmodul.cpp(114) : {353} client block at 0x000FED48, subtype c0, 64 bytes long.
a CDynLinkLibrary object at $000FED48, 64 bytes long
a CDynLinkLibrary object at $000FED48, 64 bytes long
{352} normal block at 0x000FEB78, 416 bytes long.
 Data: <ÍÍÍÍÍÍÍÍ        > CD CD CD CD CD CD CD CD 00 00 00 00 00 00 00 00
{351} normal block at 0x000FEB40, 8 bytes long.
 Data: < ÍÍÍxë  > 01 CD CD CD 78 EB 0F 00
{341} client block at 0x0041ECC0, subtype c0, 64 bytes long.
a CDynLinkLibrary object at $0041ECC0, 64 bytes long
a CDynLinkLibrary object at $0041ECC0, 64 bytes long
{255} client block at 0x0041E328, subtype c0, 64 bytes long.
a CDynLinkLibrary object at $0041E328, 64 bytes long
a CDynLinkLibrary object at $0041E328, 64 bytes long
f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\strcore.cpp(156) : {249} normal block at 0x000F9148, 22 bytes long.
 Data: <´¦!j            > B4 A6 21 6A 05 00 00 00 05 00 00 00 01 00 00 00

[ad nauseum...]

f:\dd\vctools\vc7libs\ship\atlmfc\src\mfc\strcore.cpp(156) : {71} normal block at 0x000F1E10, 26 bytes long.
 Data: <´¦!j                  > B4 A6 21 6A 09 00 00 00 09 00 00 00 01 00 00 00
Object dump complete.
FPMgr deleted.
The program '[6632] ForecastProTRAC.exe: Native' has exited with code 0 (0x0).

Apr 13, 2011 at 6:44 PM

I have exactly the same problem. And no clue to why this is not working... I am jumping back to 2.0b.

Apr 14, 2011 at 4:14 PM

For reporting problems, none of us will get anywhere, if you fail to produce bug reports missing all of information that's needed to reproduce anything. All that I, or KindDragon can surmise from this is it didn't work. Sorry, but I nor K.D. can't help unless we have more info.

I also use VLD, and I also contribute to it too. And I find bugs in it too. But my bug reports contain lots of information. So for starters:

1. What version of VLD are you using? (release number, change list number, etc...)

2. What OS are you running on?

3. What build configuration are you running your app in? (32 / 64 bit?)

4. What is your INI file configuration?

5. Repro steps???

Apr 14, 2011 at 4:19 PM

I am running Windows 7 64 bit, vs 2010 and I used VLD 2.1 32 bit. I only compiled my application with this version and suddenly it didn't work. But coincidentally windows update also installed a few updates that might had broken it.

So I installed visual studio 2010 SP1 which took a while. I also grabbed the latest version of VLD from the repo and just compiled and used that. It all works fine now. Thanks.

Apr 14, 2011 at 4:22 PM

1.  I was running 2.1 (also tried 2.0 B)

2. I am on Win 7 x64

3. 32 bit build config

4. INI config is the default config

5.  Can't tell you.  I don't know where the memory leaks are to know where to look to give reproduction steps

Apr 14, 2011 at 4:40 PM

1. I'm also running 2.1.

2. and Win 7 x64

3. Both 32-bit and 64-bit configurations result in the same inconsistency between VS2010SP1 and VLD.

4. Default config.

5. Running a relatively simple MDI app, simply opening the program, NOT loading any saved documents or doing anything whatsover, then exiting.

Thanks, Chris, but I wonder if these aren't simply false positives mistakenly identified by VS2010SP1.

Attempting to identify the leak allocations manually leads me to tool tips on my mainframe that are introduced by MFC, so I'm not too concerned that they'd be cumulative (!).

Apr 16, 2011 at 7:29 PM
MalcolmX wrote:

5. Running a relatively simple MDI app, simply opening the program, NOT loading any saved documents or doing anything whatsover, then exiting.

Can you post this app exe and, if you can, source files?

Apr 20, 2011 at 10:36 AM

I have found a pretty serious error inside VLD that may be contributing to this. I have a currently open task dealing with this. Stay tuned.