- FixedFixed an issue where some recent Windows builds falsely reported signed Deleaker binaries as unsigned.
Changelog
Stay up to date - subscribe to the Deleaker changelog feed
Latest release
Version 2026.1 - Released January 20, 2026
2026
2025
- AddedSupport for Qt Creator 18.0.1.
- AddedSupport for Visual Studio 2026.
- AddedSupport for Qt Creator 18.0.0.
- Addednew option --snapshot-name for DeleakerConsole.exe to specify the snapshot name.
- AddedSupport for Qt Creator 17.0.2.
- FixedFixed an issue in DeleakerConsole.exe where the snapshot file contained no data when both --export-xml-report-on-exit and --snapshot-database options were specified.
- FixedResolved an issue where, when Deleaker was enabled in Visual Studio 2022, Git prompted for username and password on every operation.
- AddedSupport for RAD Studio 13.
- AddedSupport for Qt Creator 17.0.1.
- AddedExported snapshot XML is now formatted with indentation and line breaks for better readability.
- AddedSupport for Qt Creator 17.0.0.
- AddedSupport for Qt Creator 16.0.2.
- AddedSupport for Qt Creator 16.0.1.
- AddedSupport for RAD Studio 12.3 (64-bit).
- AddedSupport for Qt Creator 16.0.0.
- AddedSupport for Qt Creator 15.0.1.
- FixedThe Deleaker installer no longer ignores the components specified with the /COMPONENTS switch.
2024
- FixedFixed an issue where Deleaker could not detect leaks in binaries compiled with the new 'modern' 64-bit C++ compiler (bcc64x.exe) and where such binaries would crash at startup.
- FixedFixed an issue where Visual Studio 2022 version 17.12.3 failed to load the Deleaker extension.
- AddedSupport for Qt Creator 15.
- AddedSupport for Qt Creator 14.0.2.
- AddedVisual Studio 2022 was missing from the list of supported editors in the standalone version of Deleaker.
- AddedSupport for Qt Creator 14.0.1.
- AddedSupport for Qt Creator 14.0.0.
- AddedSupport for Qt Creator 13.0.2.
- AddedSupport for Qt Creator 13.0.1.
- AddedSupport for Qt Creator 13.0.0.
- FixedThe standalone Deleaker is now high DPI aware.
- FixedQt Creator versions prior to 12 were unable to load the Deleaker plugin.
- AddedSupport for Qt Creator 12.0.2.
- FixedThe DLLs for the extension for Visual Studio 2019 and 2022 were not signed.
2023
- FixedDeleaker was unable to detect the release of BSTR if BSTR_UserFree or BSTR_UserFree64 was used.
- AddedSupport for Qt Creator 12.0.1.
- AddedSupport for Qt Creator 12.
- AddedSupport for RAD Studio 12.0.
- AddedSupport for Qt Creator 11.0.3.
- FixedDeleaker was unable to read the large-sized DWARF debug information.
- AddedSupport for Qt Creator 11.0.2.
- AddedSupport for Qt Creator 11.0.1.
- AddedSupport for Qt Creator 11.0.0.
- AddedSupport for Qt Creator 10.0.2.
- AddedSupport for Qt Creator 10.0.1.
- FixedIssue where certain file, event, and mutex handles were missing from snapshots.
- AddedSupport for Qt Creator 10.0.0.
- FixedIn some cases, Deleaker failed to capture the freeing of memory when it was performed by delete/delete[] in C++Builder-generated binaries.
- AddedSupport for Qt Creator 9.0.2.
- FixedThe FLS client application would keep running even after exiting the Deleaker command line tool.
2022
- AddedSupport for Qt Creator 9.0.1.
- AddedThe Deleaker command line tool no longer displays unnecessary information regarding communication with the floating license server.
- AddedSupport for Qt Creator 9.0.0.
- FixedThe Deleaker command line tool can now properly recognize a floating license server.
- FixedDeleaker now correctly includes all region handles (HRGN) in a snapshot.
- AddedSupport for Qt Creator 8.0.2.
- FixedDeleaker now recognizes and accepts a local license even when a floating license server is disabled in the options.
- AddedSupport for Qt Creator 8.0.1.
- AddedDeleaker now has support for floating license servers.
- AddedSupport for Qt Creator 8.0.0.
- AddedSupport for Qt Creator 7.0.2.
- FixedDeleakerClientApi_TakeSnapshot() was previously ignoring the specified snapshot name.
- AddedSupport for Qt Creator 7.0.1.
- AddedSupport for Qt Creator 7.
- AddedIn case the VSIXInstaller.exe (in silent mode) fails to install Deleaker on Visual Studio 2017 or later, the installer now provides an option to install it manually.
- FixedOccasionally, Deleaker erroneously reported a timer-queue timer handle leak despite a successful DeleteTimerQueueTimer call.
- AddedSupport for Qt Creator 6.0.2.
- FixedDeleaker now successfully resolves symbols for binaries built by GCC 11.2.
2021
- FixedDebuggee process may crash if a DLL, built by C++ Builder, is loaded at a non-default image base.
- FixedDeleaker now correctly identifies duplicated handles.
- AddedSupport for Qt Creator 6.0.1.
- FixedDeleaker was sometimes unable to resolve stack entries generated by .NET modules.
- AddedSupport for Qt Creator 6.
- FixedDeleaker now correctly identifies a leak of the HBITMAP even when GetIconInfo, GetIconInfoExW, or GetIconInfoExA sets ICONINFO::hbmColor to zero, indicating it is null.
- AddedSupport for Qt Creator 5.0.3.
- FixedDeleaker was unable to run in Visual Studio 2017 and 2019.
- AddedSupport for Visual Studio 2022.
- AddedSupport for Qt Creator 5.0.2.
- AddedSupport for Qt Creator 5.0.1.
- AddedDeleaker menu items now include icons in RAD Studio 11.0.
- AddedSupport for RAD Studio 11.0.
- AddedSupport for Qt Creator 5.0.0.
- AddedSupport for Qt Creator 4.15.2.
- FixedSometimes, the Deleaker extension for C++ Builder would fail to locate a file in a project while opening it in the IDE. This issue occurred even when the file was already added to the project, leading Deleaker to prompt the user to specify the file's location.
- FixedThere were instances where Deleaker was unable to write files to the default working directory.
- AddedSupport for Qt Creator 4.15.1.
- FixedThe Deleaker extension for Visual Studio 2017/2019 was not displaying the help correctly.
- AddedSupport for Qt Creator 4.15.
- AddedSupport for Qt Creator 4.14.2.
- AddedSupport for Qt Creator 4.14.1.
- AddedSupport for variables $path$ and $line$ in the Options - Settings - Editor - Current Editor section.
- FixedDeleaker now retrieves correct line numbers for addresses when using DWARF debugging data information.
- FixedDebugger execution in Qt Creator would occasionally stop when using a 64-bit version of cdb.exe to debug a 32-bit process.
- FixedDeleaker may incorrectly retrieve call stacks for 64-bit processes on Windows 8.1.
- AddedImproved intermediate functions list to assist in locating the code that produces a memory leak.
- FixedThe resource usage graph now correctly displays the current working set size instead of the peak working set size.
2020
- FixedThe Deleaker plugin for Qt Creator has been fixed to prevent crashes.
- AddedSupport for Qt Creator 4.14.
- AddedThe Deleaker plugin for Qt Creator now supports the current theme of Qt Creator.
- FixedDeleaker incorrectly reported ATOM leaks in some cases.
- AddedSupport for Qt Creator 4.13.3.
- AddedDeleaker now displays the source file name and line number in the call stack.
- AddedDeleaker now supports DWARF debugging data information placed in a separate file.
- AddedDeleaker now demangles function names for 64-bit binaries compiled using Delphi and C++ Builder.
- AddedDeleaker now demangles function names for binaries compiled by Delphi and C++ Builder.
- AddedWhen the Deleaker plugin for RAD Studio needs to open a source file, it will search in directories specified in Tools - Options - Library - Browsing Path.
- AddedFixed an issue where the 64-bit version of Qt Creator sometimes failed to load Deleaker.
- AddedAdded support for 64-bit versions of Qt Creator.
- AddedAdded support for Qt Creator 4.13.2.
- FixedFixed an issue where Deleaker incorrectly showed a leak when DeleteObject was called for HDC allocated by CreateCompatibleDC.
- AddedAdded support for custom environment variables in the standalone version of Deleaker.
- FixedFixed an issue where Deleaker incorrectly showed incorrect offsets of stack entries for 32-bit binaries compiled by Delphi and C++ Builder.
- AddedAdded support for Qt Creator 4.13.1.
- FixedFixed an issue where the Deleaker window was blank in RAD Studio 10.4.1.
- AddedAdded support for Qt Creator 4.13.
- AddedAdded support for Qt Creator 4.12.4.
- FixedFixed an issue where Deleaker sometimes failed to resolve addresses if the debugging data format was DWARF.
- FixedFixed an issue where Deleaker failed to find a leak made in a lambda if mingw32 was used.
- FixedFixed an issue where Deleaker created unnecessary mutex for each thread.
- AddedAdded support for Qt Creator 4.12.3.
- FixedFixed an issue where Deleaker showed a leak if fopen() was called, but a file was not opened.
- FixedFixed an issue where Deleaker showed a leak of an atom if AddAtom() was called twice with the same name, despite DeleteAtom() being called.
- AddedAdded support for Qt Creator 4.12.2.
- AddedImproved the speed of taking a snapshot.
- AddedDeleaker now supports RegisterExpectedMemoryLeak, UnregisterExpectedMemoryLeak, SysRegisterExpectedMemoryLeak, SysUnregisterExpectedMemoryLeak for Delphi / C++ Builder.
- AddedDeleaker now supports RAD Studio 10.4.
- AddedAdded support for Qt Creator 4.12.1.
- FixedFixed an issue where a process being debugged might crash if SafeArrayCopy was called with null.
- FixedFixed an issue where the installer didn't detect Qt Creator 4.12.0 in some cases.
- FixedFixed an issue where RAD Studio might crash sometimes when opening source code.
- AddedAdded support for Qt Creator 4.12.0.
- AddedAdded support for Qt Creator 4.11.2.
- FixedFixed an issue where Deleaker would crash immediately after taking a snapshot if an old snapshot was previously loaded.
- AddedFixed an issue where Deleaker for Delphi would display incorrect leaks if memory was reallocated using ReallocMem and the pointer was changed, and later ReallocMem with zero size was called.
- AddedFixed an issue where Deleaker for Delphi would show incorrect leaks if memory was reallocated using ReallocMem and the pointer was changed.
- AddedDeleaker now shows the size of BSTR and SAFEARRAY.
- AddedAdded support for Qt Creator 4.11.1.
- FixedFixed an issue where Deleaker would show a leak of HGRN if it was passed to GetDCEx and the flags DCXINTERSECTRGN or DCXEXCLUDERGN were used.
- FixedFixed an issue where the Delphi objects list was not populated when a snapshot was loaded.
- FixedFixed an issue where executables built by C++ Builder with CodeGuard enabled might crash under Deleaker.
2019
- FixedFixed an issue where Deleaker might show incomplete call stacks for 32-bit binaries built by MinGW.
- AddedAdded support for Qt Creator 4.11.0.
- FixedFixed an issue where the Deleaker installer failed to detect an installed Qt Creator if it was installed using an online installer.
- FixedFixed an issue where a process might crash if Deleaker was attached to it and a DLL built by Delphi was loaded.
- FixedFixed an issue where Deleaker would display incorrect size despite the size of a Delphi object not being available.
- FixedFixed an issue where a DLL built by Delphi / C++ Builder might crash under Deleaker.
- AddedAdded support for Qt Creator 4.10.1 and 4.10.2.
- FixedFixed an issue where the Deleaker plugin for Qt Creator failed to find leaks for a 32-bit process if the 64-bit version of cdb.exe was used.
- FixedFixed an issue where Deleaker failed to process COFF symbols in some cases.
- FixedFixed an issue where Deleaker might show incorrect symbol status for modules.
- FixedFixed an issue where sometimes the Delphi Objects view was not shown despite the snapshot containing Delphi objects.
- FixedFixed an issue where the Deleaker plugin for C++ Builder failed to open a source file in the editor.
- FixedFixed an issue where Deleaker did not show some leaks made by 64-bit binaries built by C++ Builder.
- AddedAdded support for Qt Creator 4.10.
- AddedDeleaker now shows hidden allocations count and total allocations count.
- FixedFixed the object count of Delphi classes in snapshots difference.
- FixedFixed an issue where the Terminate button did not terminate a process in Deleaker standalone.
- AddedAdded the ability to display Delphi objects.
- FixedFixed an issue where Deleaker might get incorrect call stacks for 64-bit processes on Windows 10 build 1903.
- AddedAdded the ability for Deleaker to hang RAD Studio 10.3.2 while debugging a 64-bit process.
- AddedAdded the ability for Deleaker to crash under RAD Studio 10.3.2.
- AddedAdded support for RAD Studio 10.3.2.
- FixedFixed an issue where the Deleaker installer might detect that RAD Studio 10.2 was available despite it not being installed.
- FixedFixed an issue where the Deleaker plugin for RAD Studio crashed when a user double-clicked on a stack entry with no source file information.
- FixedFixed an issue where Deleaker might not find leaks of some allocated objects in Delphi.
- AddedAdded the ability to sort by line number as well as by source file.
- FixedFixed an issue where if the Deleaker extension was disabled in VS2017/2019, the Deleaker window would still be shown on the next restart of Visual Studio.
- AddedAdded columns "Sequence Id" and "Thread Id".
- FixedFixed an issue where Deleaker saved timestamps with milliseconds part.
- FixedFixed an issue where Deleaker might show an incorrect call stack for an allocated object in Delphi and C++ Builder.
- AddedOptimized disk space usage when debugging a 64-bit process.
- FixedFixed an issue where executables built by C++ Builder might crash on Windows 10 under Deleaker.
- AddedAdded support for Qt Creator 4.9.1 and 4.9.2.
- FixedFixed an issue where the Deleaker installer sometimes tried to install the Deleaker extension to a Visual Studio version that is not installed.
- FixedFixed an issue where the Deleaker window was not displayed correctly if Visual Studio was configured for per-monitor DPI awareness.
- FixedFixed an issue where Deleaker might report leaks despite PropVariantClear() being called.
- AddedImproved caching of DWARF debugging information in Deleaker for faster performance.
- FixedImproved the opening of Visual Studio asynchronously to prevent UI freezing in Deleaker Standalone.
- FixedFixed an issue where if Deleaker Standalone opened Visual Studio to show source code, Visual Studio was closed when Deleaker Standalone exited.
- FixedFixed an issue where "Show Source Code" in the context menu of the call stack didn't work.
- AddedImproved caching of DWARF debugging information in Deleaker.
- FixedFixed an issue where DeleakerConsole.exe might fail to save a report to an XML file.
- AddedDeleakerConsole.exe now shares options with Deleaker Standalone.
- FixedFixed an issue in Deleaker for RAD Studio where it did not ask the user for a file again if it had been chosen previously.
- FixedFixed an issue where Deleaker might not properly update the resource usage graph in RAD Studio.
- FixedFixed an issue where the Deleaker window was shown in Visual Studio despite it being disabled.
- FixedFixed an issue where the uninstaller was trying to remove Deleaker from Visual Studio where Deleaker was not installed.
- AddedAdded support for the DWARF debugging data format.
- AddedIntegration with Qt Creator.
- FixedFixed an issue where Deleaker was unable to start on Windows XP.
- FixedFixed an issue where Deleaker was incompatible with some RAD Studio extensions.
- FixedFixed an issue where the Visual Studio 2017 / 2019 debugger might hang if Deleaker is enabled.
- FixedFixed an issue where RAD Studio showed an error "The BRCC32 task failed unexpectedly" if IDE Fix Pack is installed.
- FixedFixed an issue where RAD Studio might cause crashes of rundll32.exe processes while taking a snapshot.
- FixedFixed an issue where RAD Studio might hang while debugging 64-bit applications.
- AddedAdded support for Visual Studio 2019.
- FixedFixed an issue where the Deleaker extension for RAD Studio failed to monitor leaks in a 64-bit process.
- FixedFixed an issue where the Deleaker extension for RAD Studio failed to show the source file of a leak in some cases.
- AddedImproved locating the full path of the *.dpr file if a leak is in this file.
- FixedFixed an issue where Visual Studio and RAD Studio might show first-chance exceptions while debugging.
- AddedAdded integration with RAD Studio.
- FixedFixed an issue where executables built by C++ Builder might crash under Deleaker.
- FixedFixed an issue where Deleaker might hide a leak of a thread handle returned by CreateThread().
2018
- FixedFixed an issue where Deleaker Standalone didn't navigate to the correct line number if the current editor was Visual Studio 2017.
- FixedFixed an issue where sometimes Deleaker couldn't finish taking a snapshot.
- FixedFixed an issue where timestamps were shown in local time instead of UTC.
- AddedImproved the speed of taking snapshots.
- FixedFixed an issue where in some cases Deleaker was unable to update symbols for CLR modules.
- FixedRenamed some options to avoid confusion.
- FixedFixed an issue where Deleaker showed a leaked timer despite the window associated with the timer being destroyed.
- AddedAdded new options to DeleakerConsole.exe - --snapshot-database, --dont-overwrite-snapshot-database, and --save-snapshot-period.
- AddedAdded a new option to DeleakerConsole.exe - --save-snapshot-on-exit.
- AddedImproved the speed of taking snapshots.
- FixedFixed an issue where a process might crash after attaching to Deleaker.
- AddedImproved the speed of debugging 64-bit processes.
- FixedFixed an issue where sometimes Deleaker didn't track the following user objects: HCURSOR, HACCELL, and HHOOK.
- FixedIn Visual Studio with Deleaker, if "unmanaged code profiling mode" is enabled and an unmanaged application starts a managed application, the managed application fails to start.
- AddedAdded documentation for DeleakerConsole.exe.
- FixedFixed a possible crash at startup.
- FixedFixed resizing mode of the Deleaker controls.
- AddedImproved the "profiler mode" panel.
- FixedOn Windows XP, Deleaker might show a leak of a handle despite it being freed by FindCloseChangeNotification.
- FixedThe .NET profiler didn't show parameter types of functions.
- AddedIf the source file path is saved in the PDB file with incorrect case, Deleaker passes the correct path to an editor.
- AddedAdded resource usage graph.
- AddedAdded a new option --crash-dump-directory to DeleakerConsole.exe.
- AddedDeleaker is now able to resolve stack entries that belong to managed code for unmanaged allocations.
- FixedIf the user clicked on Filters - Hide Known Leaks, Deleaker did not update the allocations list.
- FixedDeleaker failed to start on Windows XP.
- FixedDeleaker might hang while saving a snapshot to a file.
- FixedIf the user saved a snapshot to a file and the file already existed, it was not overwritten.
- FixedDeleaker did not update the list of allocations if the user clicked on Filters - Show Known Leaks.
- FixedVisual Studio 2017 might hang at startup after Deleaker installation.
- FixedImproved the speed of collecting CLR objects.
- FixedDeleaker was unable to attach to MFC applications with CLR support built by Visual Studio 2017.
- FixedDeleaker did not find leaks made by LoadImage / LR_DEFAULTCOLOR.
- AddedImproved the local help.
- AddedAdded local help.
- FixedDeleakerConsole.exe crashed if some arguments for the application to debug are specified in the command line.
- FixedDeleaker might crash while preparing a report of allocated .NET objects.
- AddedDeleakerConsole.exe is now available to run Deleaker from the console. It creates a leak report in XML format upon process exit.
- FixedDeleaker showed incorrect stack entries after correct stack trace for 64-bit processes.
- FixedDeleaker might crash while comparing snapshots.
- AddedOptimized snapshot database size.
- FixedIf "Fast mode of tracking allocations" is set to False, Deleaker crashes if the process being debugged is 64-bit.
- FixedInstallation failed for Visual Studio 2017.
- FixedDeleaker showed 'no leaks' for all modules in the modules combobox despite there being some leaks.
- FixedThe uninstaller might show the error "Windows cannot find '..\IDE\devenv'. Make sure you typed the name correctly, and then try again.".
- AddedImproved speed.
- AddedImproved speed.
2017
- AddedImproved speed.
- AddedA shadow stack is now shown for a .NET object.
- FixedWhen Deleaker was disabled in Visual Studio, it showed a dialog to choose allocation types to monitor.
- AddedAdded a mutex allocated by RegisterApplicationRestart() to known leaks.
- FixedDeleaker showed a leak if memory for PROPVARIANT::caub::pElems was allocated and PropVariantClear() was called.
- FixedDeleaker standalone might crash after processing all allocations.
- FixedIf memory was allocated by GlobalAlloc(GMEM_ZEROINIT) and freed by HeapFree(), Deleaker showed a leak.
- FixedIf the source file's path contained a space, it couldn't be opened from Deleaker Standalone.
- FixedSometimes Deleaker locked up while snapshots were being removed.
- FixedIf snapshots were compared, Deleaker showed no processes in the process list.
- AddedIf symbols settings have changed, Deleaker offers to update symbols of a snapshot.
- FixedDeleaker Standalone ignored the working directory.
- FixedLocalReAlloc crashed in some cases.
- FixedAlthough LocalFree() was called, Deleaker showed a leak produced by FormatMessage().
- FixedSymbols were not loaded from Microsoft Symbol Servers.
- FixedIf the user sets an empty or invalid path as the "Symbols cache directory" in the Options, Deleaker would crash.
- FixedSymbols were not being loaded from directories specified in "Symbol File Locations".
- Fixed64-bit processes might crash when loading/unloading a lot of DLLs.
- FixedProcesses might crash under Deleaker on Windows 10 update 1709.
- FixedA 64-bit process might crash under Deleaker.
- FixedSometimes Deleaker for Visual Studio 2017 failed to install/update.
- FixedIf the size of texts, apps, and other items is set to 175% in the display settings, some UI elements would be displayed incorrectly.
- FixedDeleaker didn't detect leaks of HBITMAP made by GetIconInfo, GetIconInfoExW, and GetIconInfoExA.
- AddedAdded stack trace information to XML reports.
- FixedFixed typos in the messages section of the installer.
- AddedAdded Visual Studio 2017 to the editors list in Deleaker Standalone.
- FixedA custom editor wouldn't run in Deleaker Standalone.
- FixedThe installer attempted to register DeleakerSDK64.dll (a 64-bit module) on 32-bit Windows and displayed an error. However, DeleakerSDK64.dll shouldn't be registered on 32-bit Windows, so no error is shown now.
- AddedIf VSIXInstaller.exe (in silent mode) fails to install Deleaker on Visual Studio 2017, the installer now offers to install it manually.
- AddedAdded 'typeinfo::name' to track leaks. TypeId name was reported as a leak. According to https://msdn.microsoft.com/en-us/library/70ky2y6k(v=VS.90).aspx, the pointer returned by typeinfo::name() should never be directly deallocated, so it's a known leak.
- AddedDeleaker now profiles .NET code.
- FixedThe uninstaller didn't remove Deleaker from Visual Studio 2017.
- FixedDeleaker showed wrong leak made by FindNextFile.
- AddedImproved detection if Visual Studio 2017 is installed or not.
- FixedA process may hang when being debugged with Deleaker.
- FixedDeleaker didn't properly handle a call of VariantClear() with VARIANTs array on Windows 10.
- AddedDeleaker now fully supports partial PDB files generated by Visual Studio 2017.
- AddedDeleaker now supports Visual Studio 2017.
- FixedDeleaker showed wrong leak made by FindNextFile.
- FixedIf the Working Directory ended with a slash, Deleaker Standalone couldn't start debugging.
- AddedSupported fast memory allocations tracking for 64-bit processes.
- FixedDeleaker showed wrong values for columns "thread id" and "value" when displaying snapshots difference.
- AddedDeleaker now tracks HENHMETAFILE handles allocated by SetEnhMetaFileBits.
- AddedAdded a new column to show the timestamp.
- AddedAdded a new column to show the process ID.
- FixedFixing mistakes in English and improving the text, here is the revised changelog:
2016
- FixedWhen a 64-bit application was being debugged by Visual Studio with Deleaker, sometimes a message about a first-chance exception could be seen. Depending on Visual Studio settings, Visual Studio might stop execution, but now such exceptions are handled by Deleaker and hidden from the user.
- FixedDeleaker showed incorrect stack entries for system 64-bit DLLs.
- FixedDeleaker showed false leaks when std::unique_lock<std::mutex> was used.
- FixedDeleaker couldn't download symbols from external servers.
- FixedCrashed if the user selected "remove snapshot" or "remove all snapshots".
- AddedNew Visual Studio "15" is supported.
- FixedIf a column that was used to sort allocations was going to be hidden, then the sort mark was shown on the next column, but actually, allocations were not resorted. Now allocations are being resorted using the next column.
- FixedIn Visual Studio, Deleaker asked for allocation types by mistake when the developer continued execution after a breakpoint.
- FixedDeleaker crashed if a module was added to excluded modules using the context menu of an allocation.
- FixedDeleaker didn't update allocations if a module was added to excluded modules (or removed from the list) using the context menu of a module.
- AddedA user can select leak types that will be monitored by Deleaker.
- AddedA user can add a function to "know leaks" from a stack entry's context menu.
- AddedDeleaker immediately updates the allocation list after adding a function to "know leaks". Previous versions required taking a snapshot again.
- AddedVisual C++ Team made some changes with respect to /DEBUG:FASTLINK starting with Visual Studio 2015 Update 1 CTP. A new kind of PDB file is introduced (a partial PDB). Deleaker supports it.
- AddedDeleaker binaries are now code signed.
- FixedDeleaker Extension used the VS color scheme even if the option "Use Visual Studio color scheme" was set to False.
- AddedNew experimental option "Fast mode of tracking heap allocations".
- FixedIf a column was hidden and shown again, the data for the column was not displayed.
- AddedA developer can select required columns in the allocation list.
- FixedSometimes Deleaker couldn't take a snapshot.
- AddedSaving and loading snapshots to a file.
- AddedExporting leaks to an XML file.
- AddedNew Client API function: DeleakerClientApi_IgnoreLeaks(). Just add DeleakerClientApi.h and DeleakerClientApi.cpp from the Deleaker installation directory\DeleakerClientApi to your project and call DeleakerClientApiIgnoreLeaks(TRUE) to disable leak monitoring for the current thread, and call DeleakerClientApiIgnoreLeaks(FALSE) to enable it. You can also use the helper class DeleakerClientApi::CIgnoreLeaks to automatically disable/enable leak monitoring.
- AddedNow it is possible to remove a snapshot or all snapshots.
- AddedNew Client API functions: DeleakerClientApi_TakeSnapshotForCurrentThread and DeleakerClientApi_TakeSnapshotForProcessThread.
- AddedA Client API: Now it is possible to make Deleaker take a snapshot directly from the application code. Just call the function DeleakerClientApi_TakeSnapshot() from DeleakerClientApi.h (available in Deleaker installation directory\DeleakerClientApi).
- FixedIf a lot of threads are being created and terminated, Deleaker might consume a lot of memory.
- FixedChanged the icon of the "compare with" (compare snapshots) button, as it was almost invisible if the dark scheme was enabled in Visual Studio.
- FixedA quick fix, there were two incorrect DLLs in the installer.
- AddedBeing run on Windows 10, Deleaker no longer requires the installation of .NET 2.0.
- FixedSetTimer() leaked by mistake if it's called again for some timer id and this timer id is returned.
- AddedNew option 'Collect leaks on process termination'. If disabled, Deleaker doesn't collect leaks for a process that has been terminated.
- FixedFalse leaks shown for pipe handles created by CreatePipe.
- AddedIf the environment variable "DeleakerEnable" is set to "0", then Deleaker is disabled. If it is set to "1", then Deleaker is enabled. This is useful for using in batch files to temporarily enable or disable Deleaker.
2015
- AddedAdded 'setlocale' to known leaks.
- FixedDeleaker crashes if the working directory points to a network location.
- FixedDeleaker Standalone couldn't properly attach to a process on 32-bit Windows.
- FixedA process being debugged under Deleaker crashes in VariantClear() if a passed VARIANT contains SAFEARRAY of BSTR strings and at the same time field 'parray' is NULL.
- FixedDeleaker may hang during loading symbols.
- AddedNew option "intermediate functions" to better find the source of an allocation.
- FixedStack trace was not updated if one clicked on a column to sort allocations.
- AddedEnable/disable filters via context menu of the allocation list and the module list.
- AddedAdd a module to exception list via context menu.
- AddedA button with a drop-down menu to enable/disable filters quickly.
- FixedDeleaker incorrectly considered handles returned by CreateMetaFile and CreateEnhMetaFile as HENHMETAFILE / HMETAFILE instead of HDC. If CloseMetaFile / CloseEnhMetaFile were called, Deleaker still showed leaks of HDC.
- AddedSome processes may crash when Deleaker tries to attach to them.
- AddedYou can view symbol load information for a module.
- FixedDeleteTimerQueueTimer was not handled properly.
- AddedNew option "Max stack depth" allows you to set how many stack entries can be saved for allocations.
- AddedContext menus for allocations, stack entries, and modules.
- AddedDouble click on an allocation shows the source code.
- FixedDeleaker didn't hide allocations made by a module even if its name was included in Options - Exceptions - Excluded Modules - Excluded Names.
- AddedNow Deleaker is able to extract function name from the symbol name to make it possible to hide leaks if the function name is not provided.
- FixedDeleaker hides allocations that are made in OnDestroy() of MFC CDialog derived class.
- FixedSometimes Deleaker hangs during loading allocations.
- FixedAfter loading a snapshot, the sort arrow icon disappeared.
- FixedIf a snapshot diff is shown, modules information in the "Modules" tab is empty.
- FixedThe allocation list was not updated sometimes if one selected a module to filter allocations.
- FixedIf a window was destroyed, its timers still leaked.
- FixedKnown leaks are not shown regardless of whether Options - Exceptions - Known Leaks - "Hide known leaks" is enabled or not.
- AddedModules Tab shows information about modules and their symbols.
- FixedDeleaker extension didn't show allocations on VS 2015 / Win 10.
- AddedVS 2015 is supported.
- FixedIf a process being debugged with Deleaker Standalone throws an exception, then the process exits despite a handler existing. Now the execution continues.