New Post: No Leaks Detected in CLR application (vs 2010)

January 2, 2014, 2:10 am

≫ Next: Source code checked in, #b79142a5958d4e48081081cb085e466fb49d7a11

≪ Previous: New Post: No Leaks Detected in CLR application (vs 2010)

Another interesting repro is this:
Create a new project using the 'MFC Application' template, and add a leak somewhere (say in the InitInstance) like

BOOL CSimpleMfcAppApp::InitInstance()
{
        int* thisShouldLeak = new int(5);
        ...

As expected, this gets reported by both the default leak detection and by vld if enabled.

Now go on project properties and change the 'Common Language Runtime Support' option from 'No Common Language Runtime Support' to 'Common Language Runtime Support (/clr)'

The builtin leak detection will still report the leak.
But if you enable vld (by adding #include "vld.h") you will have a sad

No memory leaks detected.
Visual Leak Detector is now exiting.

Let me know if there is anything I can do to help fixing this

↧

Source code checked in, #b79142a5958d4e48081081cb085e466fb49d7a11

January 8, 2014, 4:13 pm

≫ Next: New Comment on "Frequently Asked Questions"

≪ Previous: New Post: No Leaks Detected in CLR application (vs 2010)

PatchModule crash fixed in some situations

↧

New Comment on "Frequently Asked Questions"

January 11, 2014, 8:04 am

≫ Next: New Post: LINK: fatal error LINK1104: cannot open file "vld.lib"

≪ Previous: Source code checked in, #b79142a5958d4e48081081cb085e466fb49d7a11

I am having the exact same problem. I have moved the PDB file around to different directories too.

↧

New Post: LINK: fatal error LINK1104: cannot open file "vld.lib"

January 14, 2014, 3:29 am

≫ Next: Closed Issue: DLL CRT initialization leaks [10421]

≪ Previous: New Comment on "Frequently Asked Questions"

Hi,

i kind of have a similar issue. I have a cmake buildet toolkette under vc2008 windows xp. The projects base on a same framwork but work independently. Some of them can be builded with vld but the other not. Non of them use definitions in windows.h direktly.

Without any change in my code or vld.h i received errors from Microsoft_SDKs and told me there are ambiguous symbols. Since i cannot change the namespace i tried to include windows.h before vld.h. Then i received the Link error: cannot open file 'vld.lib'.

Maybe someone has any idea how can i fix it or how can the vld not denpendent on windows.h any more?

Thanks a lot!

↧

Closed Issue: DLL CRT initialization leaks [10421]

January 17, 2014, 12:39 pm

≫ Next: Edited Issue: DLL CRT initialization leaks [10421]

≪ Previous: New Post: LINK: fatal error LINK1104: cannot open file "vld.lib"

When VLD is linked with a DLL, it reports quite some leaks in initialization routines. After some exploration, it seems that CRT allocates some memory to hold environment variables, argv etc. and does not bother to free them (since it is not needed as they live through whole lifetime of a module).

The problem is that these leak reports pollute debug output window possibly hiding any actual leaks in a library. Is it possible to hide them somehow? I tried to use VLDMarkAllLeaksAsReported at the beginning of DllMain function but it also hides all executable leaks before that (using LoadLibrary). I build against static CRT in VS 2008.

I leave this issue to a discussion as this behavior is technically correct (CRT actually leaks memory) but there should be a way to ignore these leaks as well as they are "by design".

Example output:

WARNING: Visual Leak Detector detected memory leaks!
Visual Leak Detector detected 54 memory leaks in heap 0x00D10000

---------- Block 62 at 0x00D10A30: 164 bytes ----------
Call Stack:
f:\dd\vctools\crt_bld\self_x86\crt\src\onexit.c (208): InstUp.dll!__onexitinit + 0x15 bytes
f:\dd\vctools\crt_bld\self_x86\crt\src\crt0dat.c (953): InstUp.dll!_initterm_e + 0x7 bytes
f:\dd\vctools\crt_bld\self_x86\crt\src\crt0dat.c (297): InstUp.dll!_cinit + 0xF bytes
f:\dd\vctools\crt_bld\self_x86\crt\src\dllcrt0.c (132): InstUp.dll!_CRT_INIT + 0x19 bytes
f:\dd\vctools\crt_bld\self_x86\crt\src\dllcrt0.c (312): InstUp.dll!__DllMainCRTStartup + 0x11 bytes
f:\dd\vctools\crt_bld\self_x86\crt\src\dllcrt0.c (281): InstUp.dll!_DllMainCRTStartup + 0x11 bytes
0x77329950 (File and line number not available): ntdll.dll!RtlQueryEnvironmentVariable + 0x241 bytes
0x7732D8C9 (File and line number not available): ntdll.dll!LdrResSearchResource + 0xB4D bytes
0x7733681C (File and line number not available): ntdll.dll!RtlGetNtVersionNumbers + 0x9B bytes
0x773352D6 (File and line number not available): ntdll.dll!RtlSetUnhandledExceptionFilter + 0x50 bytes
0x77329E79 (File and line number not available): ntdll.dll!LdrInitializeThunk + 0x10 bytes
Data:
D8 32 D1 00 00 00 00 00 2C 3D 52 50 D0 00 00 00 .2...... ,=RP....
80 00 00 00 02 00 00 00 3E 00 00 00 FD FD FD FD ........ >.......
10 3E E0 45 10 3E E0 45 10 3E E0 45 10 3E E0 45 .>.E.>.E .>.E.>.E
10 3E E0 45 10 3E E0 45 10 3E E0 45 10 3E E0 45 .>.E.>.E .>.E.>.E
10 3E E0 45 10 3E E0 45 10 3E E0 45 10 3E E0 45 .>.E.>.E .>.E.>.E
10 3E E0 45 00 00 00 00 00 00 00 00 00 00 00 00 .>.E.... ........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ........ ........
FD FD FD FD ........ ........

---------- Block 12 at 0x00D11F80: 67 bytes ----------
Call Stack:
f:\dd\vctools\crt_bld\self_x86\crt\src\stdenvp.c (127): InstUp.dll!_setenvp + 0x14 bytes
f:\dd\vctools\crt_bld\self_x86\crt\src\dllcrt0.c (132): InstUp.dll!_CRT_INIT + 0xE bytes
f:\dd\vctools\crt_bld\self_x86\crt\src\dllcrt0.c (312): InstUp.dll!__DllMainCRTStartup + 0x11 bytes
f:\dd\vctools\crt_bld\self_x86\crt\src\dllcrt0.c (281): InstUp.dll!_DllMainCRTStartup + 0x11 bytes
0x77329950 (File and line number not available): ntdll.dll!RtlQueryEnvironmentVariable + 0x241 bytes
0x7732D8C9 (File and line number not available): ntdll.dll!LdrResSearchResource + 0xB4D bytes
0x7733681C (File and line number not available): ntdll.dll!RtlGetNtVersionNumbers + 0x9B bytes
0x773352D6 (File and line number not available): ntdll.dll!RtlSetUnhandledExceptionFilter + 0x50 bytes
0x77329E79 (File and line number not available): ntdll.dll!LdrInitializeThunk + 0x10 bytes
Data:
78 1E D1 00 E0 1F D1 00 B0 71 52 50 7E 00 00 00 x....... .qRP~...
1F 00 00 00 02 00 00 00 0C 00 00 00 FD FD FD FD ........ ........
41 4C 4C 55 53 45 52 53 50 52 4F 46 49 4C 45 3D ALLUSERS PROFILE=
43 3A 5C 50 72 6F 67 72 61 6D 44 61 74 61 00 FD C:\Progr amData..
FD FD FD ........ ........

Comments: Duplicate of issue https://vld.codeplex.com/workitem/10446

↧

Edited Issue: DLL CRT initialization leaks [10421]

January 17, 2014, 12:39 pm

≫ Next: Reopened Issue: DLL CRT initialization leaks [10421]

≪ Previous: Closed Issue: DLL CRT initialization leaks [10421]

↧

Reopened Issue: DLL CRT initialization leaks [10421]

January 17, 2014, 12:40 pm

≫ Next: Edited Issue: DLL CRT initialization leaks [10421]

≪ Previous: Edited Issue: DLL CRT initialization leaks [10421]

↧

Edited Issue: DLL CRT initialization leaks [10421]

January 17, 2014, 12:40 pm

≫ Next: New Post: Application gets stuck in startup

≪ Previous: Reopened Issue: DLL CRT initialization leaks [10421]

↧

New Post: Application gets stuck in startup

January 19, 2014, 7:53 am

≫ Next: New Post: Visual Leak Detector and matlab

≪ Previous: Edited Issue: DLL CRT initialization leaks [10421]

I had exactly the same problem. In fact commenting the line #include <vld.h> in all the cpp files was fixing it.
I solved the problem by copying (NOT moving)
Visual Leak Detector\bin\dbghelp.dll
into the executable directory, which I forgot to do.
The wrong dll was being loaded,

Hope it helps.

↧

New Post: Visual Leak Detector and matlab

January 22, 2014, 2:52 am

≫ Next: New Post: (File and line number not available): (Module name unavailable)!(Function name unavailable)

≪ Previous: New Post: Application gets stuck in startup

Hi,

I'm trying to use VLD with my program that links with a .dll compiled with Matlab Compiler. When I call a function of this .dll and VLD is enabled, my app fails. Does anyone tried VLD with a Matlab DLL?

Thanks in advance!

A fatal error has been detected by the Java Runtime Environment:

EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00000000774208c5, pid=6084, tid=5784

JRE version: 6.0_17-b04

Java VM: Java HotSpot(TM) 64-Bit Server VM (14.3-b01 mixed mode windows-amd64 )

Problematic frame:

C [ntdll.dll+0x508c5]

An error report file with more information is saved as:

C:\asdfasdfsadfsa\hs_err_pid6084.log

If you would like to submit a bug report, please visit:

http://java.sun.com/webapps/bugreport/crash.jsp

Opening log file: C:\Users\hjhjhj\AppData\Local\Temp\java.log.6084

↧

New Post: (File and line number not available): (Module name unavailable)!(Function name unavailable)

January 23, 2014, 2:50 pm

≫ Next: Commented Unassigned: report typeid().name() memory leak when link use static CRT [10554]

≪ Previous: New Post: Visual Leak Detector and matlab

Hello,

VLD sees that my application has leaks however I don't get the line numbers or the function names. Below is a sample output. I'm VS2012. Any ideas?

ARNING: Visual Leak Detector detected memory leaks!
---------- Block 51 at 0x0BE341F0: 19 bytes ----------
Call Stack:

0x6DBF2CF7 (File and line number not available): clr.dll!(Function name unavailable)
0x0B92EEF0 (File and line number not available): (Module name unavailable)!(Function name unavailable)
0x0D81D10A (File and line number not available): (Module name unavailable)!(Function name unavailable)
0x0D81C888 (File and line number not available): (Module name unavailable)!(Function name unavailable)
0x0D81B57B (File and line number not available): (Module name unavailable)!(Function name unavailable)
0x0D81A8C9 (File and line number not available): (Module name unavailable)!(Function name unavailable)
0x0CD320C4 (File and line number not available): (Module name unavailable)!(Function name unavailable)
0x0CD319DF (File and line number not available): (Module name unavailable)!(Function name unavailable)
0x0CD1F878 (File and line number not available): (Module name unavailable)!(Function name unavailable)
0x0CD196D7 (File and line number not available): (Module name unavailable)!(Function name unavailable)
0x0CD194B9 (File and line number not available): (Module name unavailable)!(Function name unavailable)
0x0CD114E5 (File and line number not available): (Module name unavailable)!(Function name unavailable)
0x0CCEF047 (File and line number not available): (Module name unavailable)!(Function name unavailable)
0x0CCEEB3E (File and line number not available): (Module name unavailable)!(Function name unavailable)
0x6CE4CACF (File and line number not available): mscorlib.ni.dll!(Function name unavailable)
0x6CE423D7 (File and line number not available): mscorlib.ni.dll!(Function name unavailable)
0x6CE42316 (File and line number not available): mscorlib.ni.dll!(Function name unavailable)
0x6CE422D1 (File and line number not available): mscorlib.ni.dll!(Function name unavailable)
0x6CE4CB4C (File and line number not available): mscorlib.ni.dll!(Function name unavailable)
0x6DBF2952 (File and line number not available): clr.dll!(Function name unavailable)
0x6DC1316F (File and line number not available): clr.dll!DllUnregisterServerInternal + 0x18D73 bytes
0x6DC139B5 (File and line number not available): clr.dll!DllUnregisterServerInternal + 0x195B9 bytes
0x6DCCD8B6 (File and line number not available): clr.dll!DllGetClassObjectInternal + 0x10E21 bytes
0x6DCD007D (File and line number not available): clr.dll!DllGetClassObjectInternal + 0x135E8 bytes
0x6DCD00EB (File and line number not available): clr.dll!DllGetClassObjectInternal + 0x13656 bytes
0x6DCD01B8 (File and line number not available): clr.dll!DllGetClassObjectInternal + 0x13723 bytes
0x6DBFC6DF (File and line number not available): clr.dll!DllUnregisterServerInternal + 0x22E3 bytes
0x6DCCD772 (File and line number not available): clr.dll!DllGetClassObjectInternal + 0x10CDD bytes
0x6DCD063C (File and line number not available): clr.dll!DllGetClassObjectInternal + 0x13BA7 bytes
0x7791850D (File and line number not available): KERNEL32.dll!BaseThreadInitThunk + 0xE bytes
0x77C3BF39 (File and line number not available): ntdll.dll!RtlInitializeExceptionChain + 0x85 bytes
0x77C3BF0C (File and line number not available): ntdll.dll!RtlInitializeExceptionChain + 0x58 bytes

Data:

31 2F 31 39    2F 32 30 31    34 20 32 31    3A 32 37 3A     1/19/201 4.21:27:
34 38 00                                                     48...... ........

↧

Commented Unassigned: report typeid().name() memory leak when link use static CRT [10554]

January 24, 2014, 12:42 pm

≫ Next: New Post: Is VLD bug?

≪ Previous: New Post: (File and line number not available): (Module name unavailable)!(Function name unavailable)

When link use static CRT, reported typeid(..).name() in memory leak. But when link with DLL CRT, there has no memory leak report.

VS2012 UPDATE 4

Any idea?

Sample code as follow:

#include "stdafx.h"
#include <iostream>
#include <vld.h>

class Base
{
Base() {}
~Base() {}
};

int _tmain(int argc, _TCHAR* argv[])
{
std::cout << typeid(Base).name() << std::endl;

return 0;
}

Debug Output:

Visual Leak Detector Version 2.4 installed.
'TestTypeID.exe' (Win32): Loaded 'C:\Windows\SysWOW64\imm32.dll'. Cannot find or open the PDB file.
'TestTypeID.exe' (Win32): Loaded 'C:\Windows\SysWOW64\msctf.dll'. Cannot find or open the PDB file.
WARNING: Visual Leak Detector detected memory leaks!
---------- Block 125 at 0x0061FCB8: 4272663467 bytes ----------
Call Stack:
0x7765E046 (File and line number not available): ntdll.dll!RtlAllocateHeap
f:\dd\vctools\crt_bld\self_x86\crt\prebuild\eh\typname.cpp (138): TestTypeID.exe!type_info::_Name_base + 0xC bytes
f:\dd\vctools\crt_bld\self_x86\crt\prebuild\eh\typinfo.cpp (28): TestTypeID.exe!type_info::name + 0xD bytes
c:\someworks\myworks\exercises\testversion\testtypeid\testtypeid.cpp (16): TestTypeID.exe!wmain + 0x14 bytes
f:\dd\vctools\crt_bld\self_x86\crt\src\crt0.c (241): TestTypeID.exe!__tmainCRTStartup + 0x19 bytes
f:\dd\vctools\crt_bld\self_x86\crt\src\crt0.c (164): TestTypeID.exe!wmainCRTStartup
0x76D7336A (File and line number not available): kernel32.dll!BaseThreadInitThunk + 0x12 bytes
0x77669F72 (File and line number not available): ntdll.dll!RtlInitializeExceptionChain + 0x63 bytes
0x77669F45 (File and line number not available): ntdll.dll!RtlInitializeExceptionChain + 0x36 bytes
Data:
CB 75 B9 39 EB 62 00 00 28 12 61 00 C8 FA 61 00 .u.9.b.. (.a...a.
EE FE EE FE EE FE EE FE EE FE EE FE EE FE EE FE ........ ........
EE FE EE FE EE FE EE FE EE FE EE FE EE FE EE FE ........ ........
EE FE EE FE EE FE EE FE EE FE EE FE EE FE EE FE ........ ........
EE FE EE FE EE FE EE FE EE FE EE FE EE FE EE FE ........ ........
EE FE EE FE EE FE EE FE EE FE EE FE EE FE EE FE ........ ........
EE FE EE FE EE FE EE FE EE FE EE FE EE FE EE FE ........ ........
EE FE EE FE EE FE EE FE EE FE EE FE EE FE EE FE ........ ........
EE FE EE FE EE FE EE FE EE FE EE FE EE FE EE FE ........ ........
EE FE EE FE EE FE EE FE EE FE EE FE EE FE EE FE ........ ........
EE FE EE FE EE FE EE FE EE FE EE FE EE FE EE FE ........ ........
EE FE EE FE EE FE EE FE EE FE EE FE EE FE EE FE ........ ........
EE FE EE FE EE FE EE FE EE FE EE FE EE FE EE FE ........ ........
EE FE EE FE EE FE EE FE EE FE EE FE EE FE EE FE ........ ........
EE FE EE FE EE FE EE FE EE FE EE FE EE FE EE FE ........ ........
EE FE EE FE EE FE EE FE EE FE EE FE EE FE EE FE ........ ........

Visual Leak Detector detected 1 memory leak (16925 bytes).
Largest number used: 27614 bytes.
Total allocations: 44453 bytes.
Visual Leak Detector is now exiting.

Comments: I have the same issue, has anyone been able to solve this?

↧

New Post: Is VLD bug?

January 26, 2014, 6:42 am

≫ Next: New Comment on "Documentation"

≪ Previous: Commented Unassigned: report typeid().name() memory leak when link use static CRT [10554]

I'm using VLD v2.3 with VS2010, the following is debug output:
.................................
No memory leaks detected.
Visual Leak Detector is now exiting.
Detected memory leaks!
Dumping objects ->
{19548} normal block at 0x05993470, 26 bytes long.
......................

Which should I believe, VLD or VS2010?

Any idea is appreciated, thanks.

↧

New Comment on "Documentation"

January 31, 2014, 7:07 am

≫ Next: New Post: Is VLD bug?

≪ Previous: New Post: Is VLD bug?

At long last i finally found a tool here that enables me to analyze my code. Using Ogre3d makes it very hard tracking memory-leaks with anything else besides CRTDBG, and that one doesnt really provide any useful informations. (Still found my leaks with it until now, but veeeery time-consuming). If thats ok for you, i will post your tool on the Ogre3D-page for others to find. Thanks alot for your work!!! =)

↧

New Post: Is VLD bug?

February 3, 2014, 5:02 am

≫ Next: Released: v2.2.3 (Feb 15, 2012)

≪ Previous: New Comment on "Documentation"

Vld only show memory leaks from dll's where you include vld.h. CRT always show leaks from all modules that use this CRT.

воскресенье, 26 января 2014 г. пользователь cmncoder написал:

From: cmncoder
I'm using VLD v2.3 with VS2010, the following is debug output:
.................................
No memory leaks detected.
Visual Leak Detector is now exiting.
Detected memory leaks!
Dumping objects ->
{19548} normal block at 0x05993470, 26 bytes long.
......................

Which should I believe, VLD or VS2010?

Any idea is appreciated, thanks.
Read the full discussion online.
To add a post to this discussion, reply to this email ([email removed])
To start a new discussion for this project, email [email removed]
You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe or change your settings on codePlex.com.
Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online atcodeplex.com

--
WBR,
Arkadiy Shapkin aka Dragon

↧

Released: v2.2.3 (Feb 15, 2012)

February 4, 2014, 4:25 am

≫ Next: Updated Release: v2.2.3 (фев 15, 2012)

≪ Previous: New Post: Is VLD bug?

2.2.3

Enhancements:
* New option VLD_OPT_RELEASE_CRT_RUNTIME added. Useful only with define VLD_FORCE_ENABLE.

Bugs Fixed:
* Memory leaks with static linking fixed finally.

2.2.2

Bugs Fixed:
* Memory leaks with static linking fixed.
* Visual Studio C++ 2008/2010 Express Edition compilation fixed.
* Hang fixed with GetOpenFileName().

2.2.1

Enhancements:
* strdup and _wcsdup functions support added.
* Preliminary support for VS 11 added.

Bugs Fixed:
* Low performance after upgrading from VLD v2.1.
* Runtime error R6002 fixed because of wrong memory dump format.
* version.h fixed in installer.
* Some PVS studio warning fixed.

2.2

Enhancements:
* New functions added: VLDGetLeaksCount, VLDMarkAllLeaksAsReported, VLDSetReportHook (see vld.h).
* Introduced define called VLD_FORCE_ENABLE that allows one to active VLD even if not running in DEBUG.
* Adding Heap Validation.
* _aligned... functions and _recalloc support added.
* Memory leaks additional statistic added.

Bugs Fixed:
* Issue fixed with loading wrong version of dbghelp.dll on Windows XP and bellow.
* VLDReportLeaks with aggregate duplicate links fixed.
* CoTaskMemAlloc memory leak detection fixed.
* Rare crash at exit on some platforms fixed.
* Asserts in release build disabled.
* LoaderLock fixed.
* LoadLibrary crash fixed with some applications like regsrv32.
* Callstack hash fixed with ASLR.
* VLDGlobalEnable fixed with new threads.
* Option VLD_OPT_MODULE_LIST_INCLUDE fixed.
* Resolved callstack printing fixed.

↧

Updated Release: v2.2.3 (фев 15, 2012)

February 4, 2014, 4:25 am

≫ Next: New Comment on "Using Visual Leak Detector"

≪ Previous: Released: v2.2.3 (Feb 15, 2012)

2.2.3

Enhancements:
* New option VLD_OPT_RELEASE_CRT_RUNTIME added. Useful only with define VLD_FORCE_ENABLE.

Bugs Fixed:
* Memory leaks with static linking fixed finally.

2.2.2

Bugs Fixed:
* Memory leaks with static linking fixed.
* Visual Studio C++ 2008/2010 Express Edition compilation fixed.
* Hang fixed with GetOpenFileName().

2.2.1

2.2

↧

New Comment on "Using Visual Leak Detector"

February 5, 2014, 1:54 pm

≫ Next: New Comment on "Using Visual Leak Detector"

≪ Previous: Updated Release: v2.2.3 (фев 15, 2012)

↧

New Comment on "Using Visual Leak Detector"

February 5, 2014, 2:02 pm

≫ Next: New Comment on "Using Visual Leak Detector"

≪ Previous: New Comment on "Using Visual Leak Detector"

I'm using VS2012 with Win7(x64) and having some issues setting VLD up: - Initial installation went fine. - "View ->Property Manager" needed "View ->Other Windows -> Property Manager" - "select Microsoft.Cpp.Win32.user" I have absolutely no idea where or how to do this. Property Manager is an empty form and its Properties (only active part I have found) says "There are no property pages for the selection."

↧

New Comment on "Using Visual Leak Detector"

February 5, 2014, 2:04 pm

≫ Next: Created Unassigned: Designer form crash [10556]

≪ Previous: New Comment on "Using Visual Leak Detector"

I'm using VS2012 with Win7(x64) and having some issues setting VLD up: - Initial installation went fine. - "View ->Property Manager" needed "View ->Other Windows -> Property Manager" - "select Microsoft.Cpp.Win32.user" I have absolutely no idea where or how to do this. Property Manager is an empty form saying "No Visual C++ project is loaded" and its Properties (only active part I have found) says "There are no property pages for the selection."

↧