Shulou(Shulou.com)05/31 Report--

This article will explain in detail what is the free tool to solve the Windows memory problem, the content of the article is of high quality, so the editor will share it with you for reference. I hope you will have a certain understanding of the relevant knowledge after reading this article.

Solving Windows memory problems requires an in-depth understanding of the operating system and a working understanding of how to use the Windows debugger or performance monitor. If you are trying to get details, such as kernel stack size or hard disk memory consumption, you will need complex experience with debugger commands and kernel data architectures. Even the most experienced administrators find it challenging to determine private and shared memory utilization or total stack size in the face of process address space.

Don't be afraid, RamMap and VMMap facilitate the process of solving memory problems. You can download these free tools from the Sysinternals website. Both tools are written by Mark Russinovich and Bryce Cogswell.

RamMap

RamMap is used to show system and process memory status and utilization. It provides an overview bar called usage count, which lists all kinds of system memory partitions, such as paging pools and non-paging pools, process privacy, sharable, hard disk space, kernel stack, and mapping files. It also shows the amount of memory space for cached files called Metafile.

All of these partitions are further classified into different types of physical memory consumption, such as active, standby, modified, transformed, zeroed, free, or bad. Each of these columns can be classified by clicking the column header. All these terms are explained in Russinovich's "Windows Internal Book". As shown in figure 1, the data is displayed neatly in a graphical list view.

Usage count data in figure 1:RamMap

RamMap also shows the intrinsic utilization of the process in the process column. Here you can see all the listed processes and their corresponding private memory utilization. The data also includes all process memory that takes up spare or modified page lists, as well as the amount of memory used for page table items.

Figure 2:RamMap process bar

Another use of RamMap is to show the actual physical memory usage, identifying the memory list, usage, filename, process, virtual address, and pool label page by page. Each column can be classified, and there is a filtering function that can be used to analyze data selectively.

Figure 3:RamMap physical page bar

RamMap also does a good job of showing cache file activity and data. You can use the "File Summary" and "File details" columns to look down the system file cache to determine the file path, the size it occupies, and whether the corresponding memory is in the active, spare, or modified page list.

Figure 4:RamMap file summary bar

VMMap

So far, we have seen how RamMap demonstrates system and process memory usage. If the memory problem you are trying to solve seems to be related to a specific process or application, you may need to take a closer look at it by using VMMap. VMMap is a process-oriented tool that allows you to view existing processes or track new processes and view their memory usage. It provides far more detailed information than RamMap.

When VMMap starts, it prompts you to select the current process you want to review or start a new one. If you start a new process, you will be able to track memory utilization, such as heap and virtual allocation. In figure 5 below, I selected the communicator.exe process.

Figure 5: VMMap display

Once the main window of the VMMap is displayed, you can see that the screen is divided into parts. The top section is a graphical summary of process memory consumption. It is divided into commit space, dedicated bytes, and working sets. In the middle of the screen, memory utilization is classified according to usage, such as proprietary data, shared data, pictures, mapping files, and heap size. * at the bottom of the screen, the page type corresponding to each virtual address, the size and number of working sets used, page protection, and details of all blocks and partitions are displayed. Color marking allows you to quickly see how much space is consumed by a particular type of memory.

VMMap provides two additional views of the process address space, including a "string" view and a "split" view. The string view allows you to search for all readable strings that exist in the address space. The split view shows the process virtual address space in a color-coded way, so you can see the various allocations, their size, and their continuity.

What is the free tool to solve the Windows memory problem is shared here, I hope the above content can be of some help to you, you can learn more knowledge. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.