Last edited Apr 4, 2011 at 7:50 PM by KindDragon, version 16

Comments

antonio_prove Mar 18 at 3:48 PM 
Hi, i've now installed vld on my visual studio 2010 version; i followed all instructions to use it in my projects but when i tried to built it I get an error message saying: "impossible to start the program because vld_x86.dll is not on the computer. Please try to reinstall the program". But i checked for the dll file and i found it in the bin folder of vld. Please someone can help me. Thank you

knoxus1 Jan 31 at 2:07 PM 
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!!! =)

oneeyeman Nov 5, 2012 at 10:17 PM 
Hi,
It is a good tool and it did help me even so it made a "false positive" report,
One thing though - how do I remove it from Visual Studio? I have MSVS 2010 and after pushing the directories it looks like I can't get rid of them.

yilunyou Mar 22, 2012 at 3:51 AM 
Thank you!! I've been confounded by multiple memory leaks for the past 2 weeks... the last leak so buried deep down the in 3rd party codes, i nearly gave up.. till I found this application.. you've managed to point me to the right direction.. within the hour compared to my many many hours...

Thanks!! ^^

mtpudelko Sep 14, 2011 at 2:05 PM 
This thing is AWESOME!!

You just saved me hours tracking down a few insideous leaks. Sure, I could have rolled up my sleeves and played old school WinDBG commandline, but this is a little easier on the fingers and brain.

It's a little funky with a mixed mode C++/CLI managed app with XPSP3/VS2008 32-bit (only a few classes are actually managed; the rest are native). At shutdown I consistently see an access violation in _RtlValidateHeap during ExitProcess. At least it does so only after reporting any leaks or success, so it's completely bearable with a rude finger on the stop button.

One suggestion for your documentation: It would be a little helpful for others if you mentioned the need to add \bin\xxx to the PATH environment (or have your installer add it :). It should have been obvious to me if I'd bothered to look at your install folder to actually SEE a set of \bin subdirectories, but rushing right in blindly as alway, I figured it was a happy little static library -- until, I got the failed library message. Duh!

Thank you very much for your excellent work, my crystal ball predicts it'll get my continued use :).

Regards,
Mike