Share via

ProcDump - Configurable hang timeout for -h

Martin Setnička 0 Reputation points
2026-03-25T14:01:40.9733333+00:00

Currently ProcDump uses a fixed 5-second timeout for detecting hung windows (-h). This causes false positives in large WinForms / WPF applications.

Request: Allow configurable timeout, e.g.: -h 30 or --hang-timeout 30

Sysinternals
Sysinternals

Advanced system utilities to manage, troubleshoot, and diagnose Windows and Linux systems and applications.

0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Q&A Assist
    2026-03-25T14:01:57.1133333+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    ProcDump’s hung window trigger -h uses the same definition of a window hang as Windows and Task Manager: a window that does not respond to window messages for at least 5 seconds. In the current documented version of ProcDump, this 5‑second threshold is fixed and there is no command-line option to configure or override the hang timeout.

    The available -h usage is:

    procdump -h <process>

    which:

    "Write a Mini dump for a process named 'hang.exe' when one of its windows is unresponsive for more than 5 seconds:"

    There is no documented -h <seconds> or --hang-timeout parameter, nor any other option that changes the 5‑second hang detection interval. To avoid false positives in large WinForms/WPF applications, alternative triggers (for example, CPU or memory thresholds with -c, -m, or performance counters with -p) must be used instead of -h.

    Feature requests such as making the hang timeout configurable are not currently exposed as ProcDump options in the provided documentation.

    References:

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.