Windows 10: Bug: maxed-out resources in virtual memory

We experience maxed-out resources in virtual memory when running tests with SmartBear TestExecute for longer period of times For example, a few or several dozen hours The issue was identified as a potential kernel memory leak, particularly with the Windows service RPCSS, observed during a session with the customer using Windows 10 on desktop builds. We also think that places where we’re leaking some memory is MmSt - this is for I/O caching/memory mapping. The issue was observed on Windows 10 desktop builds, not server builds, with suspicions of a kernel memory leak, particularly involving t

:)

 

Windows OS: Win32_PerfRawData_PerfProc_Process Virtual Memory is not matching with resource monitor's Commit Memory

I am trying to pull the Process metrics using Win32_PerfRawData_PerfProc_Process as documented at https://learn.microsoft.com/en-us/previous-versions/aa394323(v=vs.85)

From the document, VirtualBytes states

and PrivateBytes

I am trying to retrieve following data and compare with resource monitor output.

• "VirtualBytes"
  
• "VirtualBytesPeak"
  
• "WorkingSet"
  
• "PoolNonpagedBytes"
  
• "PoolPagedBytes"
  
• "PrivateBytes"
  
• "PageFileBytes"
  
• "PageFaultsPerSec"
  

I have consider retrieving data for powershell as example and it was running on PID=17820 (Refer to screenshot, the first row in resource monitor is powershell.exe)

-----

The Memory related values from Win32_PerfRawData_PerfProc_Process does not match with resource monitor.

-----

Python code to retrieve information using Win32_PerfRawData_PerfProc_Process and win32com.client

Python output:

• I am enclosing the screenshot of the script output as well as resource monitor.
  

• Except WorkingSet Nothing matched (Working set matches with Working (Kb) in resource monitoring.)
  
• PrivateBytes from the Win32_PerfRawData_PerfProc_Process DID NOT MATCH with Private (kb) in resource monitor. Can anyone explain why is that ?. Is PrivateBytes really map to Private(kb) in resource monitor. If not then how to compute Private(kb) that matches with resource monitoring.
  
• VirtualBytes is literally in TB very very large. Why is that so. (When I used psutil, it vms matched with Commit Kb in resource monitor)
  

psutil output for same PID 17820.

I Guess vms from psutil output matches with Commit Kb in resource Monitor.

The question is how to map the output related to memory Win32_PerfRawData_PerfProc_Process to Commit Kb in resource monitor. Am I missing something or need to do some additional math to find commit kb.?

I tried below logic, but still it did not work.

• Similarly, how to find out the Shared Memory value which is shown in resource Monitor. This has something to do with Page, Pagefiles, hence I pulled even those information, however I am unable to find Shared Memory with those data points.
  

I tried below logic, but did not work with perf data. (It works with resource Monitor, if resource monitor Private memory value is considered. if perf raw data considered, its not matching)

Can anyone help me out on this. Conceptually I guess I am missing something.

The other data points like page info, pool info, working set, peak values from Win32_PerfRawData_PerfProc_Process match with the psutil output (observe both the outputs from above) except Virtual Memory

Refer to above description, I enclosed python code. Right now trying to compare results from Win32_PerfRawData_PerfProc_Process and Resource Monitor.

 

Windows successfully diagnosed the condition of no virtual memory.

Hi, AleksanderBR

Welcome to Microsoft Community.





We understand that you are experiencing issues related to virtual memory. There are times when Windows automatically allocates to virtual memory may not be sufficient for you to use certain software, in this case, you can try to set it manually:

1. Open System Properties:

• Right-click on "This computer" or "My computer" icon and select "Properties".
  

2. Access Advanced System Settings:

• In the System Properties window, click "Advanced System Settings" on the left side.
  

3. View the performance settings:

• Under the "Advanced" tab of the "System Properties" window, click "Settings" in the "Performance" section.
  

4. Open the virtual memory settings:

• In the "Performance Options" window, click on the "Advanced" tab, then locate the "Virtual Memory" section and click "Change". Click "Change".
  

Adjust the virtual memory to the size you want to use.



Furthermore, you can submit your ideas and suggestions about Virtual memory through the Feedback Hub, and the development team will regularly review submissions for ideas or fixes.

Please share the feedback link here after submitting as it will allow others on the forum to vote for your submission, including me. More votes will lead to more visibility and higher priority to the development team.





Best Regards

Nicholas.Z| Microsoft Community Support Specialist

 

There is not enough memory or resources, MS Paint

Your first step should not be to edit the registry, this may not be the root cause.

The message says 'not enough memory or resources' so you should look at that first, the problem may be with the system, not Paint itself. Sometimes system resources do not get released for re-use once no longer needed by an app. Select Restart from the power button on Start, this will ensure Windows does a full start from cold and will have all resources available.

How much RAM do you have? What size is your page file? If you have not already done so, set the page file to 'System managed', Step 8 in this tutorial.

Manage Virtual Memory Pagefile in Windows 10

What does Task Manager show for Memory on its Performance tab while you use Paint? What is the size of the image you are editing?

If you still want to try editing the registry, then close Paint and open Regedit. Go to Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Applets\Paint. In the left hand column, right-click on Paint and select Export to save the key as a .reg file (in case you need to restore it). Then right-click on Paint and delete it. The key and all its sub-keys will be recreated when you next open Paint.