Deleaker 2019.20: Integration with Qt Creator

Today we are pleased to present our clients the next version of Deleaker. Deleaker 2019.20 is coming with the full support of Qt Creator. New version of Deleaker can work as a Qt Creator plugin helping developers to find leaks without leaving Qt Creator.

You can get Deleaker for Qt Creator right now at the download page.

It is a very important milestone in the Deleaker’s lifespan. The fact is that from the very beginning one of the most important features of Deleaker was to let a developer search for some leaks in the code without leaving the IDE.

Fortunately, Qt Creator can be extended by third party plugins. It’s time for Deleaker to be a part of Qt Creator.

Qt Creator uses either Visual C++ compiler, or MinGW, to compile C++ code. These compilers produce debugging information in different formats. Visual C++ compiler generates PDB files. MinGW uses DWARF format. Deleaker supports both formats.

Qt Creator doesn’t use its own debugger but external debuggers instead, CDB or GDB. Deleaker cooperates with any of them to receive debug events notifications.

Let’s go on. The updated installer identifies the installed versions of Qt Creator, from which you can choose the ones you would like to integrate Deleaker with:

Launch Qt Creator. In the main menu there is a new item “Deleaker”:

Deleaker menu item in Qt Creator

Let’s see how Deleaker is looking for leaks. Create a new project, introduce a leak, allocating one instance of QPushButton. Imagine that someone allocated QPushButton but then decided not to add it to a layout:

Add leak in Qt / C++

Start debugging, close the application. Deleaker automatically takes a snapshot, and we get expected list of leaks. For each leak Deleaker shows the complete call stack:

Taking Memory Snapshot

Double clicking or using the context menu makes it easy to go directly to the corresponding line of code:

Feedback is genuinely useful and unbelievably appreciated, please write us.

Deleaker 2019.2: Integration with RAD Studio. Find Leaks in Delphi and C++ Builder.

Today we are happy to announce the next Deleaker release. Deleaker 2019.2 is coming with the full support of RAD Studio: Delphi and C++ Builder.

You can get Deleaker for Delphi / C++ Builder right now at the download page.

Download Deleaker for Delphi and C++ Builder

It is a very important milestone in the Deleaker’s lifespan. The fact is that from the very beginning one of the most important features of Deleaker was to let a programmer search for some leaks in the code without leaving the IDE. If beforehand Deleaker worked as an extension in Visual Studio only, now it integrates with RAD Studio. This means that you can search for memory leaks and resource leaks in both Delphi and C++ code directly in RAD Studio. Integration with versions from RAD Studio 2007 to the newest 10.3 Rio is supported. At the same time, Deleaker Standalone successfully finds leaks in code, compiled by versions of Delphi, starting with Delphi 7, and by versions of C++ Builder, starting with C++ Builder 6.0.

Let’s go on. The updated installer identifies the installed versions of RAD Studio, from which you can choose the ones you would like to integrate Deleaker with:

Deleaker Installer for RAD Studio

Launch RAD Studio 10.3:

RAD Studio with Deleaker Splashscreen

In the main menu there is a new item “Deleaker”:

Deleaker Menu in RAD Studio

Let’s see how Deleaker finds leaks in Delphi code. Create a new project, add a button, then allocate memory in the code, executed by pressing the button:

Add some leaks

Start debugging, then press the button, close the application. Deleaker automatically takes a snapshot, and we get the correct list of leaks. For each leak Deleaker shows the complete call stack:

Taking Snapshot

Double clicking or using the context menu makes it easy to go directly to the corresponding line of code:

Go to source code

Feedback is genuinely useful and unbelievably appreciated, please write us.

Download Deleaker for Delphi and C++ Builder

Deleaker 2018.22: Resource Usage Graph

We’re excited to announce you the latest update of Deleaker that includes the resource usage graph.

Developers often ask if it’s possible to watch the memory usage of a process. Now with the help of the graph one can visually inspect the memory usage, GDI and USER32 resources, handles:

In Visual Studio the graph respects current color scheme:

You can easily switch between different resource types:

As usual updated version available on theĀ download page.