windows magnify and dwm memory issue/problem
OS: Windows 7
Bug Report (?)
Use Case: Running Magnifier in color invert mode at 1X
Problem: DWM (Desktop window manager) runs out of memory
Description:
So I recently noticed that I can run magnifier at 1X and invert the colors on the screen. This is wonderful for reading at night or in a dark room and is now my preferred method of operation.
However:
Every hour, or so, when I'm using it, the DWM crashes--it runs out of memory. When I don't have magnifier running, I can monitor the dwm process with taskman and the memory usage looks normal. When I have the magnifier running with color invert mode, however, the memory usage steadily increases under normal operation until it runs out of memory.
At this point, my fix is to run the following which kills the dwm process:
taskkill /f /im dwm*
It restarts, and the magnifier reopens and restores its previous settings. If it weren't for the 10 second delay that freezes the computer after dwm crashes, I'd be okay with
This definitely seems like a bug with Windows 7.
Is there anyone able to reproduce the issue?
Thanks.
EDIT:
To quickly reproduce the problem:
WinKey + R
type "magnify" <enter>
WinKey + (minus)
Ctrl + Alt + F
Ctrl + Alt + I
Ctrl + Shift + Esc
note the memory usage as you change windows
Re: windows magnify and dwm memory issue/problem
That's normal. If Windows was able to zoom aerodynamic effects, would be larger and slower, do not get angry or sad, that's normal. Even when going to get Core i7, 4x Crossfire Radeon 5000, Windows Aero is turned off in the lens. Regedt32 is great for solving problems. But it's hard to remember her advice to search the key name and then try to lose all their values every time you have a problem which is risky because it could cause a lot of new problems wrong.
Re: windows magnify and dwm memory issue/problem
Sorry, I've lost a lot of what you're saying in translation.
Basically, I've verified this on two of my computers, but they were of the same type, so I wanted to make sure that someone else had experienced this problem on a different machine.
You make a reference to regedit, but I can't exactly tell what you're saying. I doubt that there is a configurable area to prevent the caching and background processing while the magnifier is in use.
I posted to a forum because I couldn't find a similar thread with google, which makes me think that it's a configuration issue with my machine. Well, here it is, people-that-have-the-same-problem.
Re: windows magnify and dwm memory issue/problem
My dear friend forrestoff can I know what you are trying to convey here if your are facing any specific problem then please specify the same in detail. I hope that I can provide you the appropriate solution based on the problem that you are facing because from your earlier post I am not getting anything.
Re: windows magnify and dwm memory issue/problem
My beloved Pierson, with much bewilderment, I am sorry to say that there is not enough of both time and space to convey my complication to thee. Such prose required herein to sufficiently and succinctly contain and transfer the concept of my misfortune may only be constructed by the Gods. Perhaps it is my ineptitude that leaves much desired; perhaps the gods favor not the writer but rather the cause; perhaps my undergarments are soiled too heavily with the fruits of my labor. For I am but a fledgling in this world of grief and sorrow.
Please, my dear Pierson, I petition emphatically and fervently for your guidance and support in these times.
Re: windows magnify and dwm memory issue/problem
Have you tried to temporarily restart DWM by using the below command:
net stop uxsms
net start uxsms
Or you could also try to modify regedit
HKEY_CURRENT_USER/Software/Microsoft/ScreenMagnifier: data (MagnificationMode) = 2
[1: Docked; 2: Full Screen]
Re: windows magnify and dwm memory issue/problem
Thanks for the control hook, einstein_007. I've created a script that I'm running in the background to restart the process before it runs out of memeory. It polls tasklist every 30s and parses the size of the dwm.exe process, waiting for it to reach 1GB. At that point, it issues a net start and stop on the uxsms service.
MS really needs to fix this on their end.
(for those unfamiliar with windows scripting, save the below in a file with a .bat extension, then run it. You'll need tasklist and sleep installed, which should be windows 7 native applications.)
Code:
@echo off
rem script by forrestoff 5/18/2011
:start
for /f "tokens=5,6,7,8* delims=K, " %%i in ('tasklist^|find "dwm.exe"') do (
if not exist %%k (
echo %%i,%%j K
goto eof
) else (
set /p h=%%i,%%j,%%k K <nul
echo -- %time% --- OVER 1GB for the Process, starting it over.
net stop uxsms
net start uxsms
goto eof
)
)
:eof
sleep 30
goto start
Re: windows magnify and dwm memory issue/problem
Sorry, there's a bug in my code.
This should work:
Code:
@echo off
rem script by forrestoff 5/18/2011
:start
for /f "tokens=5,6,7,8* delims=K, " %%i in ('tasklist^|find "dwm.exe"') do (
if "%%k"=="" (
echo %%i,%%j K
) else (
set /p h=%%i,%%j,%%k K <nul
echo -- %time% --- OVER 1GB for the Process, starting it over.
net stop uxsms
net start uxsms
)
)
sleep 30
goto start