DMP output test using DebugDiag2

[iti-attunity-sup]

Hello.

The following explains how to use DebugDiag2 to output a dmp file when investigating a Qlik task crash.

https://community.qlik.com/t5/Official-Support-Articles/Collecting-Replicate-Process-Dumps/ta-p/1746...
https://customerportal.qlik.com/article/Debugging-Qlik-Replicate-Crashes

I have installed and configured DebugDiag2, and I would like to test whether a dmp file is output.
However, I don't know how to crash a task to output a dmp file.
Please tell me how to intentionally crash a task to output a dmp file.

I tried the following, but no dmp file was output.
- Taskkilling repctl.exe (QLik Replicate Server Service)
- Taskkilling repctl.exe (the Task process)

Infomation：
・Qlik Replicate November 2024
・Windows Server 2022

Best Regards.

[hugo_andrade · Accepted solution]

Hi @iti-attunity-sup ,

Create a Replication task using a Database as source, any target is fine.

After the replication task starts, stop the source server. This crashed replicate once for me.

Second:

During a task execution, reduce the priority of the Replicate process to low.

Open a very large file using VS Code or similar. This will consume RAM and trigger a crash.

Let me know the results.

[iti-attunity-sup]

Thank you for the information.

I tried both of the procedures you provided.
While the first one did not work in my environment,
the second one did, although it did not consistently generate a crash dump.
Inspired by the second idea, I explored a third approach.

For this third idea, I used the Windows API (JOBOBJECT_EXTENDED_LIMIT_INFORMATION) to set a maximum memory usage limit for repctl.exe.
By allowing repctl.exe to use a very limited amount of memory,
I was able to almost always cause a CDC task to crash and create a crash dump.

I appreciate your help,