Partager via

Process Report (Compact 2013)

  • Article

3/26/2014

The DevHealth process report displays the number of pages of certain page types that each process uses at the moment that DevHealth runs. The page types that the process report accounts for are shown in the following table.

Symbol

Meaning

S

Committed stack page for a thread.

H

Heap.

E

Writable data section in an .exe file.

D

Writable data section in a .dll file. Cannot be shared between processes.

C

Executable code in RAM.

R

Read-only data section in RAM, or RAM committed as read-only. If this read-only data is not an .exe or a .dll file, it is most likely a memory-mapped file.

W

RAM committed as read-write. Most likely mapped memory.

An example of a process report is shown in the following table, followed by an explanation of its columns.

DevHealth Process Report

The descriptions of the columns are listed below.

  • The Process column shows the name of the process.

  • The PID column shows the process ID (PID).

  • The Base column is always 0 (zero) in this report.

  • The Page? column shows whether the module is pageable or not. The descriptions of the entries in this column are listed in the following table.

    Page? column entry

    Description

    Y

    The module (.exe or .dll) is fully pageable.

    N

    The module is stored on media where it could be paged, but it is currently unpaged. This means that all of the code and data for the module is consuming RAM while the module is loaded. To make the module pageable, you have to set linker settings to allow paging or set the module to be pageable in the .bib files or driver registry settings.

    CANNOT

    The module is stored on media where it cannot be paged (usually the Release Directory File System Drive [RELFSD]), so it is unpaged. This means that all of the code and data for the module is consuming RAM while the module is loaded.

    PART

    The module is stored on media where it could be paged, but only part of the module is pageable. This is usually true of drivers that have some ISR/IST or power management code which cannot safely be paged, while the rest of the driver could be paged. The unsafe parts of the driver are reported to the linker as un-pageable, while the rest is allowed to page in order to reduce RAM consumption.

  • The Total column displays the sum of the S, H, E, D, c, r and W values in the preceding columns. This total does not include pages of type C, R, p, d, ?, P, and -, which are listed in the page summaries of the individual processes in the System Memory Map Report. Note that the process report summarizes the number of pages for certain page types, whereas the System Memory Map shows the layout.

See Also

Concepts

DevHealth Memory Use Tool