Windows 10: explorer memory leak

Hello, i have noticed rather annoying bug with explorer.exe, i was used to open folders with explorer through shellexecute with some params...windows explorer seems to be borked now, anytime it opens, it opens as a new instance and even if folder gets closed, explorer instance remains and is eating memory, its not closing, run it few times and few gigs of ram is gone 200MB per explorer instance, until explorer gets restarted manualy, can be reproduced with winexec or even with WIN+R run.steps to reproducepen task manager - details page, and sort by namenotice explorer.exe should be si

:)

 

Memory leak issue

The term "memory leak" means that an application fails to return all its RAM to the operating system when it exits. The leftover RAM is unusable to the operating system.

Step one is to identify the application that is leaking memory. Step two is to contact the application's developers and provide as much detailed data on the memory leak as you can. For example: which processes are still in RAM after the application exits
and how much RAM they occupy. Application developers never want their applications to leak memory and they will be grateful for the details you provide, particularly if they can replicate the leak on their own computers.

 

Possible Memory Leaks in Windows 10

A memory leak occurs when an application closes and fails to release all its RAM back to the operating system.

The first step in dealing with a memory leak is to determine which application is leaking memory.

The next step is to contact that application's technical support with complete details of the memory leak, since the developers will want to fix the problem ASAP.

 

Windows Explorer Memory Leak

I have multiple PC's and the leak seems to be only one AMD chipset (with CPU / GPU combo ) PC's. I have tried updating windows to the latest. I have tried updating AMD drivers to the latest. I have going onto windows performance mode under advanced settings.

I can not pinpoint the leak to a specific driver or handle within Explorer. I do note that Explorer does seem to have a handle leak. I have removed any 3rd party handles inclusive of EDGE PDF preview dll. There seems to be a commit charge constantly and Explorer will eventually reach over 1GB in working memory. I am wondering if anyone can assist in locating this issue. I have all the tools however I do not have a lot of experience in dissecting memory and or processes to this extent. I have done a lot of reading and troubleshooting before coming to these forums.

The only thing I have found that is extremely odd is that Explorer sets a commit of about 3.27MB periodically and if I do an estimate of how many of these handles under the type "Section" it roughly equals the overage in with working set memory. Reaching critical mass takes a few days, restarting explorer clears the working set memory, and RAM usage goes back to about 48% (normal). This makes me believe there is a handle leak but I can't find the cause.