New Post: Leak Report in an Empty project (Windows 7 64Bits + VS2010)
Yes, I read it. And after I move the "#include <vld.h>" to the top of the file "stdafx.h", there is no confused report any more. Thanks
View ArticleNew Post: Leak Report in an Empty project (Windows 7 64Bits + VS2010)
Yes, I find this file ok.
View ArticleCreated Unassigned: Application is crashing on start if VLD is used [10624]
Hi,I a new to VLD. I am working on Photoshop Plugin in which I want to detect the memory leaks.I installed the VLD 2.5.1 and included the vld.h file in main cpp file. I see that app crashes on start.I...
View ArticleNew Post: leak in GLSL shader...
Hi! Been getting 2 leaks because of vertexShaderSource and fragmentShaderSource but have been able to delete them using:delete[] vertexShaderSource; delete[] fragmentShaderSource; Been getting HEAP...
View ArticleNew Post: leak in GLSL shader...
This is most likely not related to VLD. My educated guess is that the code in readShader reads more byte than m_shaderCodeLenght+1. Anyway, I would suggest to not rely on char arrays when reading files...
View ArticleNew Post: leak in GLSL shader...
Thank you for your quick answer. I started with const char* because this is what compileShader() is expecting. Following your advice, I replaced it by std::string. Here below is what I am doing now, so...
View ArticleNew Post: Visual Leak Detector not recognising the Qt parent child...
Hello All, I am using link visual leak Detector (VLD)to detect the memory leaks in my C++/Qt code. Once I end the program VLD is showing Visual Leak Detector detected 7183 memory leaks (519961 bytes)....
View ArticleNew Post: Visual Leak Detector not recognising the Qt parent child...
Hi! The same problem with VLD in my Qt application. VLD detects a lot of memory leaks. My application uses Qt 5.7.1 libraries, most of leaks shows with Qt libraries. The VLD output: Visual Leak...
View ArticleCreated Unassigned: 2017 support? [10625]
Obviously, this project is described as 2008-2015 support. But on the off chance that it would work, I tried compiling with VS 2017.Understandably, this didn't work.Is there a roadmap for 2017...
View ArticleNew Post: Support of VS2017?
Any plans to support the newly released Visual Studio 2017? This is a great product and I have used it when needed on VS2012 & Vs2015. Now VS2017 calls....
View ArticleNew Comment on "Using Visual Leak Detector"
I have a native DLL which is loaded by a C# managed program and I suspect memory leaks in the native DLL. How can I use VLD to detect in memory leak in the native DLL? That native DLL allocates memorys...
View ArticleCreated Unassigned: VLD can't find pdb with relative path [10626]
I dont run my exe from the standard location in Visual Studio and have set a custom working directory vld seems to not find my PDB file even though its next to the exe.When I turn on DBGHELP_DBGOUT the...
View ArticleCommented Unassigned: VLD can't find pdb with relative path [10626]
I dont run my exe from the standard location in Visual Studio and have set a custom working directory vld seems to not find my PDB file even though its next to the exe.When I turn on DBGHELP_DBGOUT the...
View ArticleNew Comment on "Using Visual Leak Detector"
I had a project run on debug version and had memory leak issue: So VLD was installed on VS2015 - and run with Remote debugger After add "vld.h" into project, but end up "exception" and could not pin...
View ArticleCreated Unassigned: GDI+ object leaks went undetected [10627]
VLD is awesome. Still I can't it to report leaks from GDI+ objects. For example, simply doing this:```Gdiplus::GraphicsPath* p = new GraphicsPath;```This won't cause any report, altough it's a major...
View ArticleNew Post: Can VLD be used in release builds?
I know _CrtSetAllocHook doesn't exist in release builds and all debugging code for CRT memory isn't there, but I do need to make it work in release. What kind of options to I have? I'm using release...
View ArticleNew Post: Support of VS2017?
The old version actually still works for me with VS2017, but it didn't display function-names in the callstack and just showed some pointers. So I updated the dbghelp.dll in the Visual Leak Detector...
View ArticleNew Post: Support of VS2017?
Posseidon, thanks for providing a solution. I hope that official compatibility with VS2017 will be released soon.
View ArticleNew Post: Google Test memory leaking
Did anyone try to figure out Google Test (GTest) memory leak on debug build???? I did a simple Gtest No memory leaks detected. Visual Leak Detector is now exiting. Detected memory leaks! Dumping...
View ArticleNew Post: VLD does not work when the DLL project is present in the solution
Hi, I have a project which uses multiple DLLs. When I ran it under MSVC it reports memory leaks, So I downloaded latest VLD. I added the line "#include <vld.h>" to every project (all DLLs and the...
View Article