Windows 10: Paged Pool Memory Leak using _popen in timer for every 30 secs C++ application Windows

shameershaik1 · Apr 8, 2022

Below code snippet causing Paged Pool Memory leak.Whiletrue{std::shared_ptr<FILE> pipe_popencmd, "r", _pclose;Sleep30000; // 30 secs}I noticed the Paged pool increase in Task Manager and also using xPerf tool.details of the functionMy Application is NTP Client.cmd = NTP status check either SYNC or not with NTP Server

:)

comnuts · Apr 8, 2022

is this memory leak?

Hello RASHMIRANJAN1,

I'm an independent advisor and hope this would address your questions.

This is not a memory leak. A memory leak happens when a process or program failed to discard utilized memory when it is no longer in use. In that case, you would see a process or program consuming more and more memory over time.

I wouldn't be worried about the paged and non-paged pools as they aren't excessively large in size. The paged pool is used to store handles of kernel objects, so it is normal to have some usage there. And non-paged pool is used by kernel and drivers of the
operating system, so it is also normal for some usage there.

Igor Leyko · Apr 8, 2022

paged pool memory increasing over time

Hi Karim,

seems there is memory leak in someone module. Please use poolmon tool to analyze a problem.

See
https://support.microsoft.com/en-sg/help/177415... and

https://blogs.msdn.microsoft.com/ntdebugging/20...

RyougaLolakie · Apr 8, 2022

High paged pool memory after leaving system on for quite sometime

They are not the same (the paged pool contains pageable memory, the non-paged pool contains non-pageable memory). But they're both used by drivers.
Click to expand...

Oh, I see! Thanks for the clarity!

1.2 GB Paged pool does not seem unreasonable for a system with 32 GB RAM. This value is higher for systems with large RAM sizes. In any event it is hardly likely to be the cause of your problem.

The paged and non paged memory pools are used by kernel level components such as drivers and the kernel itself. The paged pool can be paged out at the memory managers discretion while the non paged pool must remain in RAM at all times. Task Manager will not tell you how much of the paged pool is in RAM.

Memory usage in any modern OS is controlled by the system memory manager, always with the goal of maximizing overall system performance. When available memory is plentiful, as is shown in the screenshots, the memory manager will allow processes and other Windows components to use pretty much whatever memory they want without restrictions. But if there is memory pressure it is fully capable of reducing the paged pool usage to a small fraction of it's current value. But it will only do this if needed. Doing it at any other time would serve no useful purpose and would likely impair performance. Note that this is the RAM resident portion of the paged pool, not what is shown in Task Manager which would be unaffected.

High memory usage, even if it is seriously abnormal, will not impair performance unless it causes a shortage. I have seen many Internet articles that get this wrong. It is not unusual for the paged pool to grow over time. Unless there is a memory leak, and there is nothing to suggest that here, this growth will stop.
Click to expand...

Pageable memory controlled by memory management...that makes ALOT of sense! Oh well, at least the page pool stops at 1.2gb memory so I still have plenty of ram leftover for multi-tasking purposes. For virtual memory, I left it at system managed on C:/ drive. Otherwise, I'll try to update the network drivers and nvidia drivers. I know Killer Network drivers are highly proneable for memory leaks.

Say, did Intel made an update of Intel Rapid Storage drivers for 4th Gen processors?

Windows 10: Paged Pool Memory Leak using _popen in timer for every 30 secs C++ application Windows

Paged Pool Memory Leak using _popen in timer for every 30 secs C++ application Windows

Paged Pool Memory Leak using _popen in timer for every 30 secs C++ application Windows

Paged Pool Memory Leak using _popen in timer for every 30 secs C++ application Windows

Paged Pool Memory Leak using _popen in timer for every 30 secs C++ application Windows - Similar Threads - Paged Pool Memory

fltMgr.sys causing an insane Paged Pool memory leak

fltMgr.sys causing an insane Paged Pool memory leak

Paged Pool Memory Leak using _popen in timer for every 30 secs C++ application Windows

Big non-paged pool memory leak at startup used by etwB

Paged/Non-Paged Pool Memory Leak?

Huge memory leak in non paged pool

Windows 10 Non-Page pool memory leak

Non paged pool memory leak

2GB Non-Paged Pool memory leak