|
Measures reported by ProcessDetailTest
This
test is used to monitor the memory leaks (if any) in any Windows application or process. This test is particularly useful in development and
staging environments, where memory leaks with applications can be detected
early and recoding done to overcome the leaks.
| Measurement |
Description |
Measurement
Unit |
Interpretation |
| Current_handles |
The
total number of file handles that are currently owned by each
thread in the process |
Number |
If
there is a consistent increase in the value of this measure over
time, then it is
a clear indicator of a memory leak in the process. |
| Private_memory |
The
resources (handles, physical RAM, the paging file, system resources,
etc.) that the process has allocated that cannot be shared with other
processes |
KB |
If
there is a consistent increase in the value of this measure over time,
then it is
a clear indicator of a memory leak in the process. |
| Pool_paged_memory |
The
memory in the paged pool. A paged pool is an area of system memory for
objects that can be written to the disk, but which must remain in the
physical memory. |
KB |
If
there is a consistent increase in the value of this measure over time,
then it is
a clear indicator of a memory leak in the process.
|
| Pool_nonpaged_memory |
The
memory in the non-paged pool. A non-paged pool is an area of system
memory for objects that cannot be written to the disk, but which must
remain in the physical memory as long as they are allocated. |
KB |
If
there is a consistent increase in the value of this measure over time,
then it is
a clear indicator of a memory leak in the process.
|
|