Softpedia >Windows >Programming >Components & Libraries >Visual Leak Detector >  Changelog

Visual Leak Detector Changelog

What's new in Visual Leak Detector 2.5.1

Sep 9, 2019
  • Enhancements:
  • PDB added to installer.
  • Bugs Fixed:
  • Fix ntdll loader patch for Windows 10 (1607) Anniversary Update causing crashes (thanks to @ioannis-e).
  • Vld dll loading order fixed with MFC.
  • Suppressible msgboxes in setup with cmdline /silent /suppressmsgboxes.

New in Visual Leak Detector 2.5 (Sep 9, 2019)

  • Enhancements:
  • VS2015 support added.
  • Windows 10 support added.
  • Support MFC 12 MBCS (thanks to @mnissl).
  • VLD config through env. vars (thanks to @akaStiX).
  • Support detection DllMain allocations (thanks to @ioannis-e).
  • Add option to skip reporting crt startup allocations as memory leaks (thanks to @ioannis-e).
  • Improve the vld.ini searching from additional locations (thanks to @ioannis-e).
  • Changed implementation of FastCallStack::getStackTrace for 32-bit code.
  • Bugs Fixed:
  • Fix #9519, #9859, #10544, use LoaderLock to serialize any calls which load additional libraries or require access to the Loader Lock (thanks to @ioannis-e).
  • Fix #6359, #10553, fix crashes and failure to register COM dlls where Visual Leak Detector is unloaded before IMalloc interface is released (thanks to @ioannis-e).
  • Fix #10548, vld.ini search path (thanks to @ioannis-e).
  • Fix #10587, Visual Leak Detector reporting strange leaks in CRT module of VC++ (thanks to @ioannis-e).
  • Fix #10588, false positives from CRT in VS2013 with /MTd (thanks to @ioannis-e).
  • Deadlock fixed with StackWalkMethod=safe.

New in Visual Leak Detector 2.2 (Jul 27, 2011)

  • 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.

New in Visual Leak Detector 2.1 (Mar 29, 2011)

  • Enhancements:
  • New functions added: VLDGlobalDisable, VLDGlobalEnable, VLDGetOptions, VLDGetReportFilename, VLDSetOptions, VLDSetModulesList, VLDGetModulesList, VLDResolveCallstacks (see vld.h).
  • Option VLD_OPT_SKIP_HEAPFREE_LEAKS added.
  • Hash for each leak added
  • Supported loading symbols from Visual Studio symbol cache directory
  • Bugs Fixed:
  • Improved LdrLoadDll, GetProcAddress hooking on Windows 7.
  • "HMODULE not founded" bug fixed.
  • Bugs fixed when VLD off.
  • Problem fixed with GetModuleHandleW for SxS dll's (mfc*.dll, msvcr*.dll).
  • Unicode-to-multibyte conversion fixed.

New in Visual Leak Detector 2.0b (Jan 18, 2011)

  • Enhancements:
  • Added new commands: VLDReportLeaks, VLDRefreshModules, VLDEnableModule, VLDDisableModule, VLDSetReportOptions (see vld.h).
  • Bugs Fixed:
  • Problems with MSVC 2008 SP1 fixed. Thanks to Laurent Lessieux for contributing this patch.
  • vld.h fixed

New in Visual Leak Detector 2.0a (Jan 18, 2011)

  • Renamed vld dll files.
  • Problem with MSVC 2010 Unicode library fixed.

New in Visual Leak Detector 2.0 (Jul 10, 2010)

  • This adds support for x64 applications and VS 2010.

New in Visual Leak Detector 1.9h Beta (Aug 4, 2009)

  • added support for VS 2008.

New in Visual Leak Detector 1.9d Beta (Sep 3, 2007)

  • Failed assertion "freed == TRUE" pops up when running a program with VLD without the debugger attached.
  • Some, but not all, multithreaded programs that dynamically load and unload many DLLs have been known to experience problems, such as deadlocks or exceptions, when used with VLD.
  • Failed assertion "exportmodule != NULL" pops up when running some programs with VLD.
  • VLD fails to show file names or function names in the memory leak report for some programs that are linked with the dynamic CRT library.
  • Access violation exceptions are thrown, but caught by the operating system, when running some programs with VLD.