Visual Leak Detector throwing "Access violation reading location" on ntdll.dll

Question

When I include:

#include <vld.h>;

in my stdafx.h and run my program it says that Visual Leak Detector 2.5 is installed. I can run my program just fine but when it exits I get this error:

Exception thrown at 0x00007FFFB7F57FE7 (ntdll.dll) in CPPAssessment.exe: 0xC0000005: Access violation reading location 0x00007FFFB8095252.

If there is a handler for this exception, the program may be safely continued.

But I only get this when I enable Visual Leak Detector so my guess is that that is the problem.

I did however find this site: Visual Leak Detector Forums And someone mentions a fix but it leads to a github repo with an vld.cpp file and I don't know what to do with it.

It seems the error was caused by the Windows 10 aniversary update but I am not sure.

Despoil

Haha, jelmer :') Ik heb het zelfde probleem... – Dispirit

I have the same problem, but my program dosnt even start. – Safire

This question actually has nothing to do with C++ or C++11. Since "Visual Leak Detector" is a third-party product, you might want to add relevant tags that will draw attention of people who use/maintain such a product. – Contango

Please try this build vld.codeplex.com/releases/view/630509 – Guildhall

Can you provide your vld.ini and activate visual leak detector find leak inside VLD. – Redress

Answer 1

VLD 2.5.1 is released in which the bug is fixed for windows 10. https://vld.codeplex.com/releases/view/630509

I waited for this from a while. Thanks to VLD team

Robertaroberto

Answer 2

If you don't really have to use vld to detect memory leaks, Dr. Memory is an option, it worked great for me on Windows, same as Valgrind.

Evelinevelina

Answer 3

Some Windows API are allocating their own memory to handle some internal data. You're probably trying to mess with that kind of memory.

In Visual Studio go to DEBUG>Exceptions... and add "Native Run-Time Checks". Your code will break when you mess with the memory. Look where you are in the call stack and investigate around your last memory modification.

I've used VLD for years and some times it look strange but it's always accurate. In case of doubt look the documentation in MSDN to be sure how the memory should be handled.

Womanhater

Answer 4

I'm facing the issue while debugging in Visual Studio 2019. I solved it deleting the hidden directory .vs and all Debug and Release directories.(VS must be closed)
After a new build everything ran fine.

Version 2.5.1 (as @hariprasad mentioned) is already installed on my computer.

Offtopic: I've several issues regarding the .vs directory. First try if I have a weird issue is to delete this folder and rebuild.

Alastair