Don't miss updates

Receive information about releases as RSS feed.

  • 8/19/2022 August 2022

    Version 2022.9

    FIX: Deleaker ignored local license although a floating license server was disabled in the options.

  • 8/16/2022 August 2022

    Version 2022.8

    ADD: Qt Creator 8.0.1 is supported.

    ADD: Deleaker supports floating license servers.

  • 7/25/2022 July 2022

    Version 2022.7

    ADD: Qt Creator 8.0.0 is supported.

  • 5/25/2022 May 2022

    Version 2022.6

    ADD: Qt Creator 7.0.2 is supported.

    FIX: DeleakerClientApi_TakeSnapshot() ignored snapshot name.

  • 5/3/2022 May 2022

    Version 2022.5

    ADD: Qt Creator 7.0.1 is supported.

  • 4/4/2022 April 2022

    Version 2022.4

    ADD: Qt Creator 7 is supported.

  • 2/1/2022 February 2022

    Version 2022.3

    ADD: if VSIXInstaller.exe (in silent mode) fails to install Deleaker on Visual Studio 2017 or later, the installer offers to install it manually.

  • 1/25/2022 January 2022

    Version 2022.2

    FIX: sometimes Deleaker reported a leak of a timer-queue timer handle, although DeleteTimerQueueTimer succeeded.

  • 1/19/2022 January 2022

    Version 2022.1

    ADD: Qt Creator 6.0.2 is supported.

    FIX: Deleaker failed to resolve symbols for binaries built by GCC 11.2.

  • 12/27/2021 December 2021

    Version 2021.23

    FIX: a debuggee process may crash if a DLL that C++ Builder built was loaded not at its default image base.

    FIX: Deleaker skipped some duplicated handles.

  • 12/21/2021 December 2021

    Version 2021.22

    ADD: Qt Creator 6.0.1 is supported.

  • 12/6/2021 December 2021

    Version 2021.21

    FIX: sometimes Deleaker failed to resolve stack entries produced by .NET modules.

    ADD: Qt Creator 6 is supported.

    FIX: If GetIconInfo, GetIconInfoExW or GetIconInfoExA put zero to ICONINFO::hbmColor, Deleaker shown a leak of the HBITMAP despite it is null.

  • 11/8/2021 November 2021

    Version 2021.20

    ADD: Qt Creator 5.0.3 is supported.

  • 11/4/2021 November 2021

    Version 2021.19

    FIX: Deleaker failed to run in Visual Studio 2017 and 2019.

  • 11/3/2021 November 2021

    Version 2021.18

    ADD: Deleaker supports Visual Studio 2022.

  • 10/11/2021 October 2021

    Version 2021.17

    ADD: Qt Creator 5.0.2 is supported.

  • 9/27/2021 September 2021

    Version 2021.16

    ADD: Qt Creator 5.0.1 is supported.

  • 9/24/2021 September 2021

    Version 2021.15

    ADD: Deleaker menu items didn't contain icons in RAD Studio 11.0.

  • 9/13/2021 September 2021

    Version 2021.14

    ADD: RAD Studio 11.0 is supported.

    ADD: Qt Creator 5.0.0 is supported.

  • 7/15/2021 July 2021

    Version 2021.13

    ADD: Qt Creator 4.15.2 is supported.

  • 7/2/2021 July 2021

    Version 2021.12

    FIX: sometimes the Deleaker extension for C++ Builder failed to find a file in a project while opening it in the IDE: although such a file was added to the project, Deleaker asked a user where the file is located.

  • 6/17/2021 June 2021

    Version 2021.11

    FIX: sometimes Deleaker is unable to write files to the default working directory.

  • 6/15/2021 June 2021

    Version 2021.10

    ADD: Qt Creator 4.15.1 is supported.

  • 5/26/2021 May 2021

    Version 2021.9

    FIX: Deleaker extension for Visual Studio 2017 / 2019 didn't display the help.

  • 4/20/2021 April 2021

    Version 2021.8

    ADD: Qt Creator 4.15 is supported.

  • 3/22/2021 March 2021

    Version 2021.7

    ADD: Qt Creator 4.14.2 is supported.

  • 3/1/2021 March 2021

    Version 2021.6

    ADD: Qt Creator 4.14.1 is supported.

  • 2/22/2021 February 2021

    Version 2021.5

    ADD: variables $path$ and $line$ are supported by Options - Settings - Editor - Current Editor.

  • 2/10/2021 February 2021

    Version 2021.4

    FIX: Deleaker retrieved incorrect line number for some addresses if DWARF debugging data information was used.

    FIX: if Qt Creator used a 64-bit version of cdb.exe to debug a 32-bit process, the debugger stopped execution from time to time.

  • 2/2/2021 February 2021

    Version 2021.3

    FIX: Deleaker might get incorrect call stacks for 64-bit processes on Windows 8.1.

  • 1/27/2021 January 2021

    Version 2021.2

    ADD: improved intermediate functions list to help better find a code that produces a leak.

  • 1/11/2021 January 2021

    Version 2021.1

    FIX: the resource usage graph shown the peak working set size instead of the current working set size.

  • 12/27/2020 December 2020

    Version 2020.33

    FIX: Deleaker plugin for Qt Creator might crash.

  • 12/18/2020 December 2020

    Version 2020.32

    ADD: Qt Creator 4.14 is supported.

  • 12/14/2020 December 2020

    Version 2020.31

    ADD: Deleaker plugin for Qt Creator supports current Qt Creator theme.

  • 12/1/2020 December 2020

    Version 2020.30

    FIX: Deleaker incorrectly reported about ATOM leaks in some cases.

    ADD: Qt Creator 4.13.3 is supported.

  • 11/8/2020 November 2020

    Version 2020.29

    ADD: Deleaker shows source file name and line number in a call stack.

    ADD: Deleaker supports DWARF debugging data information placed in a separate file.

  • 10/26/2020 October 2020

    Version 2020.28

    ADD: Deleaker demangles function names for 64-bit binaries compiled by Delphi and C++ Builder.

  • 10/16/2020 October 2020

    Version 2020.27

    ADD: Deleaker demangles function names for binaries compiled by Delphi and C++ Builder.

    ADD: when the Deleaker plugin for RAD Studio needs to open a source file, it searches in directories specified in Tools - Options - Library - Browsing Path.

  • 10/12/2020 October 2020

    Version 2020.26

    ADD: sometimes a 64-bit version of Qt Creator failed to load Deleaker.

  • 10/11/2020 October 2020

    Version 2020.25

    ADD: Deleaker supports 64-bit versions of Qt Creator.

  • 10/6/2020 October 2020

    Version 2020.24

    ADD: Qt Creator 4.13.2 is supported.

    FIX: Deleaker shown a leak if DeleteObject was called for HDC allocated by CreateCompatibleDC.

    ADD: Deleaker standalone supports custom environment variables.

  • 9/28/2020 September 2020

    Version 2020.23

    FIX: Deleaker shown incorrect offsets of stack entries for 32-bit binaries compiled by Delphi and C++ Builder.

  • 9/20/2020 September 2020

    Version 2020.22

    ADD: Qt Creator 4.13.1 is supported.

  • 9/14/2020 September 2020

    Version 2020.21

    FIX: the Deleaker window was blank in RAD Studio 10.4.1.

  • 8/31/2020 August 2020

    Version 2020.20

    ADD: Qt Creator 4.13 is supported.

  • 7/16/2020 July 2020

    Version 2020.19

    ADD: Qt Creator 4.12.4 is supported.

  • 7/8/2020 July 2020

    Version 2020.18

    FIX: sometimes Deleaker failed to resolve addresses if the debugging data format was DWARF.

    FIX: Deleaker failed to find a leak made in a lambda if mingw32 was used.

  • 7/2/2020 July 2020

    Version 2020.17

    FIX: Deleaker created unnecessary mutex for each thread.

  • 6/23/2020 June 2020

    Version 2020.16

    ADD: Qt Creator 4.12.3 is supported.

  • 6/14/2020 June 2020

    Version 2020.15

    FIX: Deleaker shown a leak if fopen() was called, but a file was not opened.

    FIX: Deleaker shown a leak of an atom if AddAtom() was called twice with the same name, despite DeleteAtom() was called.

  • 6/5/2020 June 2020

    Version 2020.14

    ADD: Qt Creator 4.12.2 is supported.

  • 6/4/2020 June 2020

    Version 2020.13

    ADD: improved speed of taking snapshot.

    ADD: Deleaker supports RegisterExpectedMemoryLeak, UnregisterExpectedMemoryLeak, SysRegisterExpectedMemoryLeak, SysUnregisterExpectedMemoryLeak for Delphi / C++ Builder.

  • 5/30/2020 May 2020

    Version 2020.12

    ADD: Deleaker supports RAD Studio 10.4.

    ADD: Qt Creator 4.12.1 is supported.

  • 5/13/2020 May 2020

    Version 2020.11

    FIX: a process being debugged might crash if SafeArrayCopy was called with null.

  • 5/12/2020 May 2020

    Version 2020.10

    FIX: the installer didn't detect Qt Creator 4.12.0 in some cases.

  • 5/6/2020 May 2020

    Version 2020.9

    FIX: RAD Studio might crash sometimes on opening source code.

  • 4/29/2020 April 2020

    Version 2020.8

    ADD: Qt Creator 4.12.0 is supported.

  • 4/1/2020 April 2020

    Version 2020.7

    ADD: Qt Creator 4.11.2 is supported.

    FIX: sometimes Deleaker crashed immediately after making a snapshot if old snapshot was loaded previously.

  • 3/23/2020 March 2020

    Version 2020.6

    ADD: Deleaker for Delphi shown incorrect leaks if memory was reallocated by ReallocMem, the pointer was changed, and later ReallocMem with zero size was called.

  • 3/17/2020 March 2020

    Version 2020.5

    ADD: Deleaker for Delphi shown incorrect leaks if memory was reallocated by ReallocMem and the pointer was changed.

  • 3/7/2020 March 2020

    Version 2020.4

    ADD: Deleaker shows size of BSTR and SAFEARRAY.

  • 2/8/2020 February 2020

    Version 2020.3

    ADD: Qt Creator 4.11.1 is supported.

    FIX: Deleaker shown a leak of HGRN if it was passed to GetDCEx and flags DCX_INTERSECTRGN or DCX_EXCLUDERGN was used.

  • 1/16/2020 January 2020

    Version 2020.2

    FIX: when a snapshot was loaded, Delphi objects list was not populated.

  • 1/13/2020 January 2020

    Version 2020.1

    FIX: executables built by C++ Builder with CodeGuard enabled might crash under Deleaker.

  • 12/18/2019 December 2019

    Version 2019.46

    FIX: Deleaker might show incomplete call stacks for 32-bit binaries built by mingw.

  • 12/16/2019 December 2019

    Version 2019.45

    ADD: Qt Creator 4.11.0 is supported.

    FIX: the Deleaker installer failed to detect an installed Qt Creator if it was installed using an online installer.

  • 12/13/2019 December 2019

    Version 2019.44

    FIX: a process might crash if Deleaker attached to it, and if a DLL built by Delphi is loaded.

  • 12/9/2019 December 2019

    Version 2019.43

    FIX: despite size of a delphi object was not available, Deleaker shown incorrect size.

  • 12/7/2019 December 2019

    Version 2019.42

    FIX: a DLL built by Delphi / C++ Builder might crash under Deleaker.

  • 12/2/2019 December 2019

    Version 2019.41

    ADD: Qt Creator 4.10.1 and 4.10.2 are supported.

  • 11/20/2019 November 2019

    Version 2019.40

    FIX: Deleaker plugin for Qt Creator failed to find leaks for 32-bit process if 64-bit version of cdb.exe was used.

  • 10/11/2019 October 2019

    Version 2019.39

    FIX: Deleaker failed to process COFF symbols in some cases.

  • 10/3/2019 October 2019

    Version 2019.38

    FIX: Deleaker might show incorrect symbol status for modules.

    FIX: sometimes Delphi Objects view was not shown despite a snapshot contained delphi objects.

  • 9/29/2019 September 2019

    Version 2019.37

    FIX: Deleaker plugin for C++ Builder failed to open source file in the editor.

  • 9/26/2019 September 2019

    Version 2019.36

    FIX: Deleaker didn't show some leaks made by 64-bit binaries built by C++ Builder.

  • 9/11/2019 September 2019

    Version 2019.35

    ADD: Qt Creator 4.10 is supported.

  • 9/3/2019 September 2019

    Version 2019.34

    ADD: Deleaker shows hidden allocations count and total allocations count.

    FIX: fixed object count of Delphi classes in snapshots difference.

  • 8/30/2019 August 2019

    Version 2019.33

    FIX: the button Terminate didn't terminate a process in Deleaker standalone.

    ADD: added displaying Delphi objects.

  • 8/21/2019 August 2019

    Version 2019.32

    FIX: Deleaker might get incorrect call stacks for 64-bit processes on Windows 10 build 1903.

  • 8/19/2019 August 2019

    Version 2019.31

    ADD: Deleaker might hang RAD Studio 10.3.2 while debugging a 64-bit process.

    ADD: Deleaker might crash under RAD Studio 10.3.2.

  • 8/18/2019 August 2019

    Version 2019.30

    ADD: Deleaker supports RAD Studio 10.3.2.

    FIX: Deleaker installer might detect that RAD Studio 10.2 was available despite it is not installed.

  • 8/13/2019 August 2019

    Version 2019.29

    FIX: Deleaker plugin for RAD Studio crashed when a user double-clicks on a stack entry with no source file information.

    FIX: Deleaker might not find leaks of some allocated objects in Delphi.

  • 8/11/2019 August 2019

    Version 2019.28

    ADD: sorting by line number as well as by source file.

    FIX: if Deleaker extension was disabled in VS2017/2019, then Deleaker window still was shown on next restart of Visual Studio.

  • 8/7/2019 August 2019

    Version 2019.27

    ADD: added columns "Sequence Id", "Thread Id".

    FIX: Deleaker saves timestamps with milliseconds part.

  • 8/6/2019 August 2019

    Version 2019.26

    FIX: Deleaker might show incorrect call stack for allocated object in Delphi and C++ Builder.

  • 7/26/2019 July 2019

    Version 2019.25

    ADD: optimized disk space usage when debugging a 64-bit process.

  • 7/9/2019 July 2019

    Version 2019.24

    FIX: executables built by C++ Builder might crash on Windows 10 under Deleaker.

  • 7/4/2019 July 2019

    Version 2019.23

    ADD: Qt Creator 4.9.1 and 4.9.2 are supported.

    FIX: sometimes the Deleaker installer tried to install the Deleaker extension to a Visual Studio version that is not installed.

  • 7/2/2019 July 2019

    Version 2019.22

    FIX: Deleaker window is not displayed correctly if Visual Studio is configured for per-monitor DPI awareness.

  • 6/30/2019 June 2019

    Version 2019.21

    FIX: Deleaker might report leaks despite PropVariantClear() was called.

  • 6/21/2019 June 2019

    Version 2019.20

    ADD: Deleaker caches DWARF debugging information faster.

  • 5/27/2019 May 2019

    Version 2019.19

    FIX: Deleaker Standalone opens Visual Studio asynchronously to prevent UI freezing.

    FIX: if Deleaker Standalone opened Visual Studio to show source code, the Visual Studio was closed when Deleaker Standalone exited.

    FIX: "Show Source Code" in the context menu of call stack didn't work.

  • 5/26/2019 May 2019

    Version 2019.18

    ADD: Deleaker caches DWARF debugging information.

  • 5/23/2019 May 2019

    Version 2019.17

    FIX: DeleakerConsole.exe might fail to save report to xml file.

    ADD: DeleakerConsole.exe shares options with Deleaker Standalone.

  • 5/19/2019 May 2019

    Version 2019.16

    FIX: Deleaker in RAD Studio does not ask a user for a file again if previously the user choosen it.

    FIX: Deleaker might not properly update resource usage graph in RAD Studio.

  • 5/16/2019 May 2019

    Version 2019.15

    FIX: Deleaker window was shown in Visual Studio despite it was disabled.

  • 5/16/2019 May 2019

    Version 2019.14

    FIX: the uninstaller was trying to remove Deleaker from Visual Studio where Deleaker was not installed to.

  • 5/14/2019 May 2019

    Version 2019.13

    ADD: DWARF debugging data format is supported.

    ADD: integration with Qt Creator.

  • 5/8/2019 May 2019

    Version 2019.12

    FIX: Deleaker was unable to start on Windows XP.

  • 5/5/2019 May 2019

    Version 2019.11

    FIX: Deleaker was incompatible with some RAD Studio extensions.

  • 4/29/2019 April 2019

    Version 2019.10

    FIX: Visual Studio 2017 / 2019 debugger might hang if Deleaker is enabled.

  • 4/10/2019 April 2019

    Version 2019.9

    FIX: RAD Studio shown error "The BRCC32 task failed unexpectedly" if IDE Fix Pack is installed.

  • 4/4/2019 April 2019

    Version 2019.8

    FIX: RAD Studio might cause crashes of rundll32.exe processes while taking snapshot.

  • 3/27/2019 March 2019

    Version 2019.7

    FIX: RAD Studio might hang while debugging 64-bit applications.

  • 3/25/2019 March 2019

    Version 2019.6

    ADD: Deleaker supports Visual Studio 2019.

  • 3/20/2019 March 2019

    Version 2019.5

    FIX: Deleaker extension for RAD Studio failed to monitor leaks of 64-bit process.

    FIX: Deleaker extension for RAD Studio failed to show source file of a leak in some cases.

  • 3/17/2019 March 2019

    Version 2019.4

    ADD: imroved locating *.dpr file's full path if a leak is in this file.

  • 3/12/2019 March 2019

    Version 2019.3

    FIX: Visual Studio and RAD Studio might show first-chance exceptions while debugging.

  • 3/11/2019 March 2019

    Version 2019.2

    ADD: integration with RAD Studio.

    FIX: executables built by C++ Builder might crash under Deleaker.

  • 2/6/2019 February 2019

    Version 2019.1

    FIX: Deleaker might hide leak of thread handle returned by CreateThread().

  • 12/15/2018 December 2018

    Version 2018.40

    FIX: Deleaker Standalone didn't navigate to correct line number if current editor was Visual Studio 2017.

  • 11/28/2018 November 2018

    Version 2018.39

    FIX: sometimes Deleaker couldn't finish taking snapshot.

  • 11/14/2018 November 2018

    Version 2018.38

    FIX: timestamps are shown in local time instead of UTC.

  • 10/12/2018 October 2018

    Version 2018.37

    ADD: improved speed of taking snapshots.

  • 8/30/2018 August 2018

    Version 2018.36

    FIX: in some cases Deleaker was unable to update symbols for CLR modules.

  • 7/30/2018 July 2018

    Version 2018.35

    FIX: renamed some options to avoid confusing.

  • 7/13/2018 July 2018

    Version 2018.34

    FIX: Deleaker shown a leaked timer despite the window associated with the timer was destroyed.

  • 6/28/2018 June 2018

    Version 2018.33

    ADD: new DeleakerConsole.exe's options --snapshot-database, --dont-overwrite-snapshot-database and --save-snapshot-period.

  • 6/26/2018 June 2018

    Version 2018.32

    ADD: new DeleakerConsole.exe's option --save-snapshot-on-exit.

  • 6/25/2018 June 2018

    Version 2018.31

    ADD: improved speed of taking a snapshot.

    FIX: a process might crash after attaching to Deleaker.

  • 6/21/2018 June 2018

    Version 2018.30

    ADD: improved speed of debugging 64-bit processes.

  • 5/3/2018 May 2018

    Version 2018.29

    FIX: sometimes Deleaker didn't track the following user objects: HCURSOR, HACCELL and HHOOK.

  • 4/26/2018 April 2018

    Version 2018.28

    FIX: in Visual Studio with Deleaker: if "unmanaged code profiling mode" enabled, and an unmanaged application starts a managed application, the managed application fails to start.

  • 4/23/2018 April 2018

    Version 2018.27

    ADD: added documentation for DeleakerConsole.exe

  • 4/19/2018 April 2018

    Version 2018.26

    FIX: fixed a possible crash at startup.

  • 4/18/2018 April 2018

    Version 2018.25

    FIX: fixed resizing mode of the Deleaker controls.

    ADD: improved "profiler mode" panel.

  • 4/17/2018 April 2018

    Version 2018.24

    FIX: on Win XP Deleaker might show a leak of a handle despite it was freed by FindCloseChangeNotification.

  • 4/13/2018 April 2018

    Version 2018.23

    FIX: the .Net profiler didn't show parameter types of functions.

    ADD: if source file path is saved in PDB file in incorrect case, Deleaker passes correct path to an editor.

  • 4/9/2018 April 2018

    Version 2018.22

    ADD: added resource usage graph.

  • 4/6/2018 April 2018

    Version 2018.21

    ADD: added new option --crash-dump-directory to DeleakerConsole.exe.

  • 4/2/2018 April 2018

    Version 2018.20

    ADD: Deleaker is able to resolve stack entries that belong to managed code for unmanaged allocations.

    FIX: if user clicked Filters - Hide Known Leaks, Deleaker didn't update the allocations list.

  • 3/30/2018 March 2018

    Version 2018.19

    FIX: Deleaker failed to start on Windows XP.

  • 3/27/2018 March 2018

    Version 2018.18

    FIX: Deleaker might hang while saving a snapshot to a file.

    FIX: if user saved a snapshot to a file and this file existed, it was not overwritten.

  • 3/25/2018 March 2018

    Version 2018.17

    FIX: Deleaker didn't update list of allocations if user clicked on Filters - Show Known Leaks.

  • 3/21/2018 March 2018

    Version 2018.16

    FIX: Visual Studio 2017 might hang at startup after Deleaker installation.

  • 3/13/2018 March 2018

    Version 2018.15

    FIX: improved speed of collecting CLR objects.

  • 3/12/2018 March 2018

    Version 2018.14

    FIX: Deleaker was unable to attach to MFC application with CLR support built by Visual Studio 2017.

  • 2/27/2018 February 2018

    Version 2018.13

    FIX: Deleaker didn't find leaks made by LoadImage / LR_DEFAULTCOLOR.

  • 2/26/2018 February 2018

    Version 2018.12

    ADD: improved local help.

  • 2/22/2018 February 2018

    Version 2018.11

    ADD: added local help.

  • 2/21/2018 February 2018

    Version 2018.10

    FIX: DeleakerConsole.exe crashed if some arguments for application to debug are specified in command line.

  • 2/21/2018 February 2018

    Version 2018.9

    FIX: Deleaker might crash while preparing a report of allocated .net objects.

  • 2/19/2018 February 2018

    Version 2018.8

    ADD: DeleakerConsole.exe is available now to run Deleaker from console. Creates a leak report in xml format on process exit.

  • 2/15/2018 February 2018

    Version 2018.7

    FIX: Deleaker shown incorrect stack entries after correct stack trace for 64-bit processes.

  • 2/14/2018 February 2018

    Version 2018.6

    FIX: Deleaker might crash while comparing snapshots.

    ADD: optimized snapshot database size.

  • 2/12/2018 February 2018

    Version 2018.5

    FIX: if "Fast mode of tracking allocations" is set to False, Deleaker crashes if process being debugged is 64-bit.

  • 2/10/2018 February 2018

    Version 2018.4

    FIX: installation failed for Visual Studio 2017.

    FIX: Deleaker shown 'no leaks' for all modules in the modules combobox despite there were some leaks.

  • 2/8/2018 February 2018

    Version 2018.3

    FIX: uninstaller might show error "Windows cannot find '..\IDE\devenv'. Make sure you typed the name correctly, and then try again.".

  • 2/7/2018 February 2018

    Version 2018.2

    ADD: improved speed.

  • 1/3/2018 January 2018

    Version 2018.1

    ADD: improved speed.

  • 12/29/2017 December 2017

    Version 2017.32

    ADD: improved speed.

  • 12/28/2017 December 2017

    Version 2017.31

    ADD: a shadow stack is shown for a .net object.

  • 12/22/2017 December 2017

    Version 2017.30

    FIX: if Deleaker was disabled in Visual Studio, it shown a dialog to choose allocation types to monitor.

  • 12/15/2017 December 2017

    Version 2017.29

    ADD: added a mutex allocated by RegisterApplicationRestart() to known leaks.

  • 12/14/2017 December 2017

    Version 2017.28

    FIX: Deleaker shown a leak, if memory for PROPVARIANT::caub::pElems was allocated, and PropVariantClear() was called.

  • 12/14/2017 December 2017

    Version 2017.27

    FIX: Deleaker standalone might crash after processing all allocations.

  • 12/12/2017 December 2017

    Version 2017.26

    FIX: if memory was allocated by GlobalAlloc(GMEM_ZEROINIT) and freed by HeapFree(), Deleaker shown a leak.

  • 12/8/2017 December 2017

    Version 2017.25

    FIX: if source file's path contained space, it couldn't be opened from Deleaker Standalone.

  • 12/6/2017 December 2017

    Version 2017.24

    FIX: sometimes Deleaker locked up while snapshots are being removed.

    FIX: if snapshots were compared, Deleaker shown no processes in the process list.

    ADD: if symbols settings have changed, Deleaker offers to update symbols of a snapshot.

  • 12/5/2017 December 2017

    Version 2017.23

    FIX: Deleaker Standalone ignored working directory.

  • 11/30/2017 November 2017

    Version 2017.22

    FIX: LocalReAlloc crashed in some cases.

  • 11/29/2017 November 2017

    Version 2017.21

    FIX: although LocalFree() was called, Deleaker shown a leak produced by FormatMessage().

  • 11/6/2017 November 2017

    Version 2017.20

    FIX: symbols were not loaded from Microsoft Symbol Servers.

  • 11/1/2017 November 2017

    Version 2017.19

    FIX: if user set empty or invalid path as "Symbols cache directory" in the Options, then Deleaker crashed.

    FIX: symbols were not loaded from directories specified in "Symbol File Locations".

  • 10/24/2017 October 2017

    Version 2017.18

    FIX: 64-bit processes might crash if they load / unload a lot of DLLs.

  • 10/24/2017 October 2017

    Version 2017.17

    FIX: processes might crash under Deleaker on Windows 10 update 1709.

    FIX: a 64-bit process might crash under Deleaker.

    FIX: sometimes Deleaker for Visual Studio 2017 failed to install / update.

  • 10/17/2017 October 2017

    Version 2017.16

    FIX: if the size of texts, apps and other items is 175% in the display settings, then some UI elements were shown weird.

  • 9/11/2017 September 2017

    Version 2017.15

    FIX: Deleaker didn't find leaks of HBITMAP made by GetIconInfo, GetIconInfoExW and GetIconInfoExA.

  • 9/8/2017 September 2017

    Version 2017.14

    ADD: added stack trace information to XML reports.

    FIX: fixed typos in the messages section of the installer.

  • 9/6/2017 September 2017

    Version 2017.13

    ADD: added Visual Studio 2017 to editors list in Deleaker Standalone.

    FIX: a custom editor didn't run in Deleaker Standalone.

  • 8/24/2017 August 2017

    Version 2017.12

    FIX: installer tried to register DeleakerSDK64.dll (a 64-bit module) on 32-bit Windows and shown error, but in fact DeleakerSDK64.dll shouldn't be registered on 32-bit Windows. No error shown now.

    ADD: if VSIXInstaller.exe (in silent mode) fails to install Deleaker on Visual Studio 2017, then installer offers to install it manually.

  • 8/21/2017 August 2017

    Version 2017.11

    ADD: added 'type_info::name' to know leaks. TypeId name was reported as leak. According to the pointer returned by type_info::name() should never be directly deallocated, so it's a known leak.

  • 8/20/2017 August 2017

    Version 2017.10

    ADD: Deleaker profiles .Net code.

    FIX: the uninstaller didn't remove Deleaker from Visual Studio 2017.

  • 3/20/2017 March 2017

    Version 2017.9

    FIX: Deleaker shown wrong leak made by FindNextFile.

    ADD: better detection if Visual Studio 2017 is installed or not.

    FIX: a process may hang being debugged with Deleaker.

  • 3/1/2017 March 2017

    Version 2017.8

    FIX: Deleaker didn't properly handle a call of VariantClear() with VARIANTs array on Win 10.

  • 2/28/2017 February 2017

    Version 2017.7

    ADD: Deleaker fully supports partial PDB files generated by Visual Studio 2017.

  • 2/22/2017 February 2017

    Version 2017.6

    ADD: Deleaker supports Visual Studio 2017.

  • 2/7/2017 February 2017

    Version 2017.5

    FIX: Deleaker shown wrong leak made by FindNextFile.

  • 2/6/2017 February 2017

    Version 2017.4

    FIX: if Working Directory ended with slash, then Deleaker Standalone couldn't start debugging.

  • 2/6/2017 February 2017

    Version 2017.3

    ADD: supported fast memory allocations tracking for 64-bit processes.

  • 1/26/2017 January 2017

    Version 2017.2

    FIX: Deleaker shown wrong values for columns "thread id" and "value" displaying snapshots difference.

  • 1/24/2017 January 2017

    Version 2017.1

    ADD: Deleaker didn't track HENHMETAFILE handles allocated by SetEnhMetaFileBits.

    ADD: added new column to show timestamp.

    ADD: added new column to show process id.

  • 10/10/2016 October 2016

    Version 3.0.112

    FIX: when a 64-bit application was being debugged by Visual Studio with Deleaker, sometimes one could see a message about first-chance exception. Depending on Visual Studio settings Visual Studio might stop execution (however the execution could be continued). Now such exceptions are handled by Deleaker and hidden from user.

  • 10/5/2016 October 2016

    Version 3.0.111

    FIX: Deleaker shown incorrect stack entries for system 64-bit DLLs.

  • 8/11/2016 August 2016

    Version 3.0.110

    FIX: Deleaker shown false leaks when std::unique_lock<std::mutex> was used.

    FIX: Deleaker couldn't download symbols from external servers.

  • 7/26/2016 July 2016

    Version 3.0.109

    FIX: crashed if user selected remove snapshot or remove all snapshots.

  • 6/30/2016 June 2016

    Version 3.0.108

    ADD: new Visual Studio "15" is supported.

    FIX: if a column that was used to sort allocations was going to be hidden, then sort mark was shown on the next column but actually allocations were not resorted. Now allocations are being resorted using next column.

    FIX: in Visual Studio Deleaker asked for allocation types by mistake when developer continued execution after a breakpoint.

  • 6/29/2016 June 2016

    Version 3.0.107

    FIX: Deleaker crashed if module was added to excluded modules using context menu of an allocation.

    FIX: Deleaker didn't update allocations if module was added to excluded modules (or removed from the list) using context menu of a module.

  • 6/20/2016 June 2016

    Version 3.0.106

    ADD: a user can select leak types that will be monitored by Deleaker.

    ADD: a user can add a function to "know leaks" from a stack entry's context menu.

    ADD: Deleaker immediately updates allocation list after adding a function to "know leaks". Previous versions required taking snapshot again.

  • 6/3/2016 June 2016

    Version 3.0.105

    ADD: Visual 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.

  • 5/27/2016 May 2016

    Version 3.0.104

    ADD: Deleaker binaries are code signed now

    FIX: Deleaker Extension used VS color scheme if VS color scheme was changed even if the option "Use Visual Studio color scheme" was set to False.

  • 5/4/2016 May 2016

    Version 3.0.103

    ADD: new experimental option "Fast mode of tracking heap allocations".

  • 4/28/2016 April 2016

    Version 3.0.102

    FIX: if a column was hidden and shown again, a data for the column was not shown.

  • 4/28/2016 April 2016

    Version 3.0.101

    ADD: a developer can select required columns in the allocation list.

  • 4/27/2016 April 2016

    Version 3.0.100

    FIX: sometimes Deleaker couldn't take a snapshot.

  • 4/25/2016 April 2016

    Version 3.0.99

    ADD: saving and loading snapshots to a file.

  • 4/15/2016 April 2016

    Version 3.0.98

    ADD: export leaks to XML file.

  • 3/3/2016 March 2016

    Version 3.0.97

    ADD: new Client API function: DeleakerClientApi_IgnoreLeaks(). Just add DeleakerClientApi.h and DeleakerClientApi.cpp from Deleaker installation directory\DeleakerClientApi to your project and call DeleakerClientApi_IgnoreLeaks(TRUE) to disable leaks monitoring for current thread, call DeleakerClientApi_IgnoreLeaks(FALSE) to enable it. Also you can use helper class DeleakerClientApi::CIgnoreLeaks to automatically disable / enable leaks monitoring:#include "DeleakerClientApi.h"...{ DeleakerClientApi::CIgnoreLeaks disable_leaks; // Do allocations in this block, Deleaker will ignore them}

  • 3/2/2016 March 2016

    Version 3.0.96

    ADD: now it's possible to remove snapshot / all snapshots.

  • 3/1/2016 March 2016

    Version 3.0.95

    ADD: new Client API functions: DeleakerClientApi_TakeSnapshotForCurrentThread and DeleakerClientApi_TakeSnapshotForProcessThread

  • 3/1/2016 March 2016

    Version 3.0.94

    ADD: a Client API: now it's possible to make Deleaker take a snapshot directly from the application code, just call function DeleakerClientApi_TakeSnapshot() from DeleakerClientApi.h (available in Deleaker installation directory\DeleakerClientApi):#include "DeleakerClientApi.h"...DeleakerClientApi_TakeSnapshot(L"Snapshot #1");... do something ...DeleakerClientApi_TakeSnapshot(L"Snapshot #2");

  • 2/22/2016 February 2016

    Version 3.0.93

    FIX: if a lot of threads are being created and terminated, Deleaker might eat a lot of memory

    FIX: changed icon of the "compare with" (compare snapshots) button, it was almost invisible if dark scheme was enabled in Visual Studio.

  • 2/5/2016 February 2016

    Version 3.0.92

    FIX: a quick fix, there were two incorrect DLLs in the installer.

  • 2/4/2016 February 2016

    Version 3.0.91

    ADD: being run on Win 10 Deleaker doesn't require to install .net 2.0 any more.

  • 2/3/2016 February 2016

    Version 3.0.90

    FIX: SetTimer() leaked by mistake if it's called again for some timer id and this timer id is returned.

  • 1/22/2016 January 2016

    Version 3.0.89

    ADD: new option 'Collect leaks on process termination'; if it's disabled, Deleaker doesn't collect leaks for a process that has been terminated.

  • 1/14/2016 January 2016

    Version 3.0.88

    FIX: false leaks shown for pipe handles created by CreatePipe.

  • 1/14/2016 January 2016

    Version 3.0.87

    ADD: if environment variable "Deleaker_Enable" is set to "0", then Deleaker disabled; if it's set to "1", then Deleaker enabled. Useful for using in batch files; to temporarily enable or disable Deleaker.

  • 12/25/2015 December 2015

    Version 3.0.86

    ADD: added 'setlocale' to known leaks

    FIX: Deleaker crashes if working directory points to a network location

  • 12/8/2015 December 2015

    Version 3.0.85

    FIX: Deleaker Standalone couldn't properly attach to a process on 32 bit Windows

  • 11/18/2015 November 2015

    Version 3.0.84

    FIX: a process being debugged under Deleaker crashes in VariantClear() if passed VARIANT contains SAFEARRAY of BSTR strings and at the same time field 'parray' is NULL

  • 11/18/2015 November 2015

    Version 3.0.83

    FIX: Deleaker may hang during loading symbols

  • 11/3/2015 November 2015

    Version 3.0.82

    ADD: new option "intermediate functions" to find a source of an allocation better

    FIX: stack trace was not updated if one clicked on a column to sort allocations

  • 10/30/2015 October 2015

    Version 3.0.81

    ADD: enable/disable filters via context menu of the allocation list and the module list

    ADD: add a module to exception list via context menu

    ADD: a button with drop-down menu to enable/disable filters quickly

  • 10/20/2015 October 2015

    Version 3.0.80

    FIX: Deleaker incorrectly considered handles returned by CreateMetaFile and CreateEnhMetaFile as HENHMETAFILE / HMETAFILE instead of HDC If CloseMetaFile / CloseEnhMetaFile were called, Deleaker still shown leaks of HDC

  • 10/20/2015 October 2015

    Version 3.0.79

    ADD: some processes may crash when Deleaker tries to attach to them

  • 10/19/2015 October 2015

    Version 3.0.78

    ADD: you can view symbol load information for a module

  • 10/16/2015 October 2015

    Version 3.0.77

    FIX: DeleteTimerQueueTimer was not handled properly

    ADD: new option "Max stack depth" allows to set how many stack entries can be saved for allocations

  • 10/8/2015 October 2015

    Version 3.0.76

    ADD: context menus for allocations, stack entries and modules

    ADD: double click on an allocation shows source code

  • 10/2/2015 October 2015

    Version 3.0.75

    FIX: Deleaker didn't hide allocations made by a module even if its name was included into Options - Exceptions - Excluded Modules - Excluded Names

    ADD: Now Deleaker is able to extract function name from symbol name to make possible hiding leaks if function name is not provided

  • 9/30/2015 September 2015

    Version 3.0.74

    FIX: Deleaker hides allocations that are made in OnDestroy() of MFC CDialog derived class.

    FIX: sometimes Deleaker hangs during loading allocations

  • 9/17/2015 September 2015

    Version 3.0.73

    FIX: after loading a snapshot, a sort arrow icon disappeared

    FIX: if a snapshot diff is shown, modules information in the "Modules" tab is empty

  • 9/9/2015 September 2015

    Version 3.0.72

    FIX: the allocation list were not updated sometimes if one selected a module to filter allocations

  • 9/2/2015 September 2015

    Version 3.0.71

    FIX: if a window was destroyed its timers still leaked

  • 8/21/2015 August 2015

    Version 3.0.70

    FIX: known leaks are not shown doesn't matter whether Options - Exceptions - Known Leaks - "Hide known leaks" enabled or not.

  • 8/13/2015 August 2015

    Version 3.0.69

    ADD: Modules Tab shows information about modules and their symbols.

    FIX: Deleaker extension didn't show allocations on VS 2015 / Win 10.

  • 7/31/2015 July 2015

    Version 3.0.68

    ADD: VS 2015 is supported

    FIX: if a process being debugged with Deleaker Standalone thrown an exception, then the process exited despite a handler exits. Now the execution continues.