dwm.exe (Desktop-Window Manager) uses high memory with Intel Intel HD Graphics 630. This problem has been reported before:
Here's a screenshot of my dwm ram usage after 2 hours (1.6 GB):
Please, this bug is already known for 3-4 months, and I do not want to reinstall a 2019 driver...
So I have tested
it has no impact on the memory leak, as I am typing right now, dwm.exe is exploding watching a video with 2mb/s again.
But it seems to fix the flicker issue I was having too since a few months.
Hi @RonaldM_Intel ,
I thank you for your priority attention on the memory leak issue caused by DWM. Pardon me for lack of updates in here, as I haven't been visiting at the forum for quite a while. Some of us have posted this issue on Microsoft forums, and unfortunately no official staff or moderator were able to respond to the issues faced by many users, or to at least caught their attention at it.
Putting aside my technical grievances, as per your instructions I have managed to downgrade my Intel GPU driver to 18.104.22.16887 and retrieved several dump files at different timestamps to roughly gauge the memory leak.
The memory leak files have been uploaded to my Google Drive here: https://drive.google.com/drive/folders/1ZT0pqbe4Nc0o5OsTExNDdtNjBz8ZyCdP?usp=sharing
The files are marked with date and timestamp (YYYYMMDD_HHmm) respectively. Starting with the following dump file sizes:
I hope these dump files would enable your debugging team a deeper look at the issue, as well as lending on your team's expertise on resolving the memory leak issue.
Understandbly, the recommendation still stands, but we as consumers feel that we shouldn't be stuck in a ping-pong or limbo situation since Microsoft isn't moving at all despite our reports being sent to them.
Once again, I enourmously appreciate your continued effort reporting and tracking this issue in the internal bug database.
Since the issue only occurs on driver versions 27.XX.XXXX and higher, I'd assume it's something to do with the WDDM 2.7, which makes sense as it was implemented early 2020.
I had the same issue here with windows 2004, CPU I7-9700K with UHD 630 and no dedicated card. dwm.exe used to ate up 20GB of my 64GB memory after hoours to days of using, which was serious while I am working in memory-intense environment. Can confirm the problem disappeared after downgrading to 10. 22.214.171.12485. Hope Intel won't remove this version of drive from the website before this issue is fixed.
Intel 10400 UHD 630 driver 126.96.36.19983 & 9079 & 9126 & 9168 memory leak.
There will be no memory leak in DWM-1, but it will start leaking after DWM-2.
Now using 188.8.131.5268.
Hope it helps you test!
My driver is lower than 184.108.40.20681, windows10 will force automatic update.
Hope Intel/Microsoft will solve it soon.
Just signed up to tell 29.20.100.XXXX drivers don't have the memory leak, after using my laptop for 8 hours my dwm.exe usage is between 80-100mb which is nothing compared to 4-6GB it used to be on previous versions.
I got this driver from some forum and the version number is 220.127.116.1116 btw I always have fast startup turned off cause I dual/triple boot other OSes on this machine.
Just made my account to say that this is happening to me too. It often occurs after about 8 hours of use. I found that putting it to sleep fixes the leak, though I think temporarily.
I might have found the solution, but this is just five or so minutes after making this discovery so it may need a trial before I can confirm.
Turn off Fast Start Up, since it seems that when I reset it, it just goes to normal but if I shut it down and turn it on with Fast Start Up on, for some reason DWM is a little more bloated. Turning off Fast Start Up will make it more akin to "resetting".
estimating the reports and views in this thread, it seems like a LOT of people have this bug, and it is unfortunate that you cannot reproduce it. From my experience as programmer, I know that bugs that cannot be reproduced are not fixable.
I have 2 suggestions how to solve this problem
#1: another user (MrX1980) posted in this thread that this problem might be fixed with windows dev build 21292, so we can delegate it to MS and hopefully they provide a fix in 21H1.
#2: what I personally would prefer is that we find out which change in your code caused the issue. I tested all public available drivers and found that the last version without this bug is 18.104.22.16876- as soon I update to the next release 22.214.171.12487 the bug occured. With a simple logarithmic search we can find the culprit version update if you are able to provide intermediate releases. But I of course do not know your company policies, like whether these are e.g., confident.
My idea is that if you provide me 126.96.36.19925, and this one bugs, I continue with 8550, if works, I test 8500 afterwards. If 8500 bugs I will test 8488. It will take maybe log2(100) = 7 tests this way to find the buggy update.
If you know the exact version, you could check the documented logs and maybe find something obvious or simply reverse the changes.
I'd be happy to help here if I can 😉
Hi! I had this issue with the latest driver as for 2/14/2021. That one was 188.8.131.5268 . Memory usage just kept increasing little by little. I downgrade it to 184.108.40.20679 and it seems fix for now. I will report anything here.
The problem persisted, I downgraded even further to Driver Version: 220.127.116.1141 . After a clean installation using DDU the memory usage has been stable for a couple of hours. I'm leaving these comments in the hope to help other people.
Most concerning is that this has been ongoing for so long, yet there seems to be no welcome fix for it?
I have a 10th gen i7 laptop which leaks from 53MB to >2GB gradually after a matter of hours until the system slows to a halt... just by doing regular things like e-mail and web surfing. Tried disabling hardware acceleration in Chrome/etc. Tried downgrading drivers (but the 630 isn't supported on the last-known non-leaking drivers of 100.6286) as well as upgrading to the latest- had 5-6 driver versions explicitly installed such as 100.9168, 100.8476, and always has the same results.
Intel- if you want a use case I'm happy to make you dump files. Just need this fixed. All of the 'solutions' here aren't solutions at all- just people restarting DWM to have it reset, or turning on full reboots which resets it to allow it to leak again.
So.. last week, I was digging into windows setting that handle scaling. then I'm turning off "Let Windows try to fix apps so they're not blurry". Now I got average 40-55MB of usage.
P.S. I have 18.104.22.16840 driver installed, Let me know if this is work on you. (sorry for bad english)
I'm turning off "Let Windows try to fix apps so they're not blurry". Now I got average 40-55MB of usage.
Where have you been all my life? This is the ONLY thing on this forum that has worked. It grew to 75MB and stayed there. Way better than 2GB.
EDIT: On the next reboot we're back over 1GB after an hour. That was a waste of time. Remains unfixed for months and between Intel and Microsoft, nobody seems to care.