forked from dmoulding/vld
-
Notifications
You must be signed in to change notification settings - Fork 315
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VLD 2.5.1 report false positive on Visual Studio 2017, MFC, Window 10 #80
Comments
So it randomly worked again. I managed to capture this. Mind you it is in Debug but it still can't pin a method signature:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have a possible false positive detection of memory leaks on window 10, vs 2017, MFC:
---------- Block 186011 at 0x0000000070C00B50: 512 bytes ----------
Leak Hash: 0x14098C6C, Count: 1, Total 512 bytes
Call Stack (TID 177604):
ucrtbased.dll!malloc_dbg()
mfc140d.dll!0x00007FFF47920001()
mfc140d.dll!0x00007FFF478A0A4B()
mfc140d.dll!0x00007FFF47707DAB()
e:\addoc iim\apuisoft dev\customer.cpp (1801): Addoc64D.exe!CCustomerApp::OnIdle() + 0xE bytes
mfc140d.dll!0x00007FFF478A0F02()
mfc140d.dll!0x00007FFF47708E13()
mfc140d.dll!0x00007FFF47920C44()
d:\agent_work\3\s\src\vctools\vc7libs\ship\atlmfc\src\mfc\appmodul.cpp (26): Addoc64D.exe!WinMain()
d:\agent_work\2\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl (107): Addoc64D.exe!invoke_main()
d:\agent_work\2\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl (288): Addoc64D.exe!__scrt_common_main_seh() + 0x5 bytes
d:\agent_work\2\s\src\vctools\crt\vcstartup\src\startup\exe_common.inl (331): Addoc64D.exe!__scrt_common_main()
d:\agent_work\2\s\src\vctools\crt\vcstartup\src\startup\exe_winmain.cpp (17): Addoc64D.exe!WinMainCRTStartup()
KERNEL32.DLL!BaseThreadInitThunk() + 0x14 bytes
ntdll.dll!RtlUserThreadStart() + 0x21 bytes
Data:
CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD ........ ........
CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD ........ ........
CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD ........ ........
CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD ........ ........
CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD ........ ........
CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD ........ ........
CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD ........ ........
CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD ........ ........
CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD ........ ........
CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD ........ ........
CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD ........ ........
CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD ........ ........
CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD ........ ........
CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD ........ ........
CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD ........ ........
CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD CD ........ ........
Visual Leak Detector detected 6 memory leaks (1704 bytes).
Largest number used: 7719945 bytes.
Total allocations: 1502986993 bytes.
Visual Leak Detector is now exiting.
Detected memory leaks!
Do you know how to skip/filter such log in the report ?
Thank
The text was updated successfully, but these errors were encountered: