Debug Diag for Memory Leaks

David_Fergen — Mon, 14 Sep 2020 18:02:39 GMT

*Note that this can't replace Replicate "getsnapshot" Command.

Download Link for Debug Diag:

In order to  define a Memory leak rule using Debug Diag follow the steps below:

1.       Open "DebugDiag X.X" (Not DebugDiag analysis/Rule builder).

2.       Under the Rules tab, click on "Add Rule…"

3.       In "Select Rule Type" Select Native Memory and handle Leak

4.       Click next and select the Process name ("Repctl.exe" in our case).

5.       In The "Configure Leak Rule" Click on "Configure".

6.       Here you can configure the triggers for the user dump -

7.       The first check box "Auto-create a crash rule.." needs to be unchecked when a Rule for crashes is already defined.

8.       Save and close.

9.       Modify the number of user dumps to 5 to prevent high disk space consumption.

10.   Click "Next".

11.   Modify the name of the rule and the Destination folder if needed.

12.   Click "Next" > Active the rule > Click "Finish".

To create dump manually:

1.       Check the PID of the problematic Task process.

2.       Open "DebugDiag X.X" (Not DebugDiag analysis/Rule builder).

3.       Switch to Processes Tab.

4.       Find the relevant PID and right click on it.

5.       Create Mini User Dump.

Make sure to attach this dump to any support cases that seems to be a memory leak.

article Debug Diag for Memory Leaks in Official Support Articles