Measures reported by AppHangEvtTest
If a process does not collect Windows messages from its queue - say, using the GetMessage function or PeekMessage function - it will be tagged as “not responding” - because it is not responding to user interface events.
This test helps quickly figure out the number and names of the ‘not responding’ processes, so that you can promptly initiate an investigation into the reason for the non-responsiveness of these processes and attack these reasons in order to restore normalcy.
The measures made by this test are as follows:
| Measurement |
Description |
Measurement Unit |
Interpretation |
| Process |
Indicates the number of processes that are not responding currently. |
Number |
A low value is desired for this measure. Ideally, the value should be 0. In case this measure reports a non-zero value, you can use the detailed diagnosis of this test to identify the processes that are not responding.
Just because a process is not responding, it does not necessarily mean that the application is actually hung -- it may just be too busy to pay attention to the user. Administrators hence need to accurately figure out why the process slipped into an ‘unresponsive’ state and then attempt to fix it. |
|