Exceptions

While most options are available for both Deleaker Standalone and Deleaker Extension for Visual Studio, some of them make sense either for the extension or standalone version only.

Legend

The following badges are used below to indicate the availability:

  •  VS  - available in Deleaker Extension for Visual Studio.
  •  Standalone  - available in Deleaker Standalone.

Contents

Excluded Modules

Excluded directories

 VS   Standalone 

If the Hide leaks from excluded modules option is True, Deleaker hides leaks that are created by the module located in an excluded directory.

Excluded names

 VS   Standalone 

If the Hide leaks from excluded modules option is True, Deleaker hides leaks that are created by the listed module.

Hide leaks from excluded modules

 VS   Standalone 

If True, Deleaker hides leaks that are created by the module listed in the excluded names list or located in an excluded directory. The default value is True.

Known Leaks

Functions

 VS   Standalone 

If the hide known leaks option is True, Deleaker hides leaks that are created by these functions.
Deleaker comes with a list of functions. Most of them are CRT functions that do one allocation being called the first time. Sometimes such allocations are not freed, and thus might be shown to user. To prevent this, Deleaker introduced the list of "known leaks".

Hide known leaks

 VS   Standalone 

If True, Deleaker hides leaks that are created by of one of known leaks functions.
The default value is True.

Misc

Hide leaks with no source code

 VS   Standalone 

If True, Deleaker hides leaks that don't have source code.

Monitorable modules

Enable monitorable modules

 VS   Standalone 

If True, Deleaker collects only allocations with stack trace containing one of the monitorable modules.
The default value is False.

Monitorable names

 VS   Standalone 

If the enable monitorable modules options is True, Deleaker collects only allocations with stack trace containing one of the module names.