![]() In both systems I have tested this the bug is not appearing, which would suggest there is another variable that is triggering the bug.Įdit: I just thought of another variable that might explain why the issue is only appearing on some computers. However, the current challenge is finding a reproducible scenario so I can report this to debug (with confidence they will be able to see the issue in their lab). Thanks for offering your help I think driver wise we already know the most important data: at least that might explain why not everyone sees the problem (perhaps they haven't received said update). I am also testing this issue on my Thinkpad T580 laptop but once again, it works fine on my side.Ĭan any of you test by doing a clean OS installation and verify if the issue occurs in that instance? It's a long shot, but I am suspecting an OS update might have introduced an update to dwm.exe that triggers the issue when paired with our new drivers. Just to explore a bit more I also tested by doing Win + Tab (several times) to launch the Desktop manager and this is the only instance I saw dwm.exe go above 200MB mark (only to go back to normal afterwards). I also used the new input from launched Spotify, PowerPoint, Word and still no reproducible scenario. I resized windows and moved around for hours to no avail. It behave normally (never going above 150MB and coming down to less than 80MB afterwards). Hi I mentioned yesterday, I left my NUC on overnight and also did once in a while a Sleep and Hibernate cycles to see if there was any change in dwm.exe memory.
0 Comments
Leave a Reply. |