Hello guys

 

After I upgraded from 1.2.5 to 1.3.1 (windows 8.1), I noticed a huge memory usage increase.

At one moment I was using 14.3 GB of RAM and 2.9 GB of VRAM ( see http://puu.sh/dukv7/e1ea9ed180.png ). 

When I closed dwm.exe my RAM usage went down to 9.5 GB and VRAM usage to 767 MB (see http://puu.sh/dukLT/54de253f35.png )

It seems that when I resize a window it keeps on allocating more memory for DWM (which isn't visible in the windows task manager) in both the RAM and VRAM. 

 

Anyone with a similar problem? 

 

 

Here's a dump of dwm.exe at the moment it used a lot of ram https://db.tt/hqWEvkgL

Edited December 14, 201411 yr by lvh1

Do you use any specific settings of Aero Glass?

 

When resizing window, DWM will resize its internal buffers - it has nothing to do with Aero Glass, DWM just needs to put whole window texture into VRAM (and the larger window is, the larger the buffer needs to be).

Do you use any specific settings of Aero Glass?

 

When resizing window, DWM will resize its internal buffers - it has nothing to do with Aero Glass, DWM just needs to put whole window texture into VRAM (and the larger window is, the larger the buffer needs to be).

No, I used the installer you provided on your website and didn't modify anything.

 

But this problem doesn't happen when I close aerohost and restart DWM though.

And when I used 1.2.5 I didn't even notice the ram/vram usage of dwm, it was negligible. 

Does it appear since the startup or does it take some time for memory to go high?

 

I found a small memory leak in the code which would appear especially when having more rendering devices, but it would be only a few hundred of kilobytes, not gigabytes.

Does it appear since the startup or does it take some time for memory to go high?

 

I found a small memory leak in the code which would appear especially when having more rendering devices, but it would be only a few hundred of kilobytes, not gigabytes.

At startup, yes. 

I've just tested it, I opened a firefox window and started resizing it and the VRAM usage went up to 3.2 GB (took about 5 seconds), after that it started filling the normal RAM. 

Edited December 14, 201411 yr by lvh1

Could you try testing this debug build? http://glass8.eu/out/DWMGlass.dll (replace old DLL - you will need to stop aerohost first and restart it from Task Scheduler after replacing).

 

When memory usage goes high, hold F11 and ensure screen redraw (e.g. move some window while holding F11). It will generate special minidump. Upload it together with debug.log which I modified to see what buffer sizes are being allocated.

Could you try testing this debug build? http://glass8.eu/out/DWMGlass.dll (replace old DLL - you will need to stop aerohost first and restart it from Task Scheduler after replacing).

 

When memory usage goes high, hold F11 and ensure screen redraw (e.g. move some window while holding F11). It will generate special minidump. Upload it together with debug.log which I modified to see what buffer sizes are being allocated.

the dump https://db.tt/p6JriN1m (its about 4GB unpacked)

and the log http://pastebin.com/BHB17GvY

 

Thanks for the help by the way. 

Edited December 14, 201411 yr by lvh1

As you can see from the debug.log, Aero Glass does not allocate so many resources - only a few buffer which gives no more than 21 MB VRAM in your case. Also, there is absolutely no reason why should the memory usage go so high. If there is some memory leak, it would grow gradually and only in the case when something more is allocated. Thus I hardly doubt that this problem is caused by Aero Glass.

As you can see from the debug.log, Aero Glass does not allocate so many resources - only a few buffer which gives no more than 21 MB VRAM in your case. Also, there is absolutely no reason why should the memory usage go so high. If there is some memory leak, it would grow gradually and only in the case when something more is allocated. Thus I hardly doubt that this problem is caused by Aero Glass.

Hmm I see, must be the combination of aeroglass and some other program then. Thanks anyway. 

capture a xperf trace of the RAM usage grow (max 1 minute):

 

http://channel9.msdn.com/Shows/Defrag-Tools/Defrag-Tools-49-WPT-Memory-Analysis-VirtualAlloc

 

and share this trace

I believe that his high RAM usage is caused by exhausting VRAM so it would be better to know if there is a way to track all VRAM allocations.

For what it's worth, on Win 8.1 I'm watching GPU-Z right now, and Memory Usage (Dedicated) and (Dynamic) hop around a little when I'm moving things or resizing things (e.g., Firefox) on the desktop, but they settle to 253 MB and 41 MB respectively if I leave things alone.  I have 3 monitors and 4960 x 1600 pixels on the desktop by the way (with ATI Catalyst 14.12; I see you have nVidia).

 

I'm forced to conclude the problem must be specific to your system somehow.

 

lvh1, do you have the latest display driver from nVidia installed?  Display driver bugs are more common than people realize, since display drivers are about the most insanely complex things on the planet.

 

-Noel

Edited December 15, 201411 yr by NoelC

I believe that his high RAM usage is caused by exhausting VRAM so it would be better to know if there is a way to track all VRAM allocations.

 

That's indeed the case here

 

For what it's worth, on Win 8.1 I'm watching GPU-Z right now, and Memory Usage (Dedicated) and (Dynamic) hop around a little when I'm moving things or resizing things (e.g., Firefox) on the desktop, but they settle to 253 MB and 41 MB respectively if I leave things alone.  I have 3 monitors and 4960 x 1600 pixels on the desktop by the way (with ATI Catalyst 14.12; I see you have nVidia).

 

I'm forced to conclude the problem must be specific to your system somehow.

 

lvh1, do you have the latest display driver from nVidia installed?  Display driver bugs are more common than people realize, since display drivers are about the most insanely complex things on the planet.

 

-Noel

I do have the latest drivers as of now (344.75) and as you say it might simply just be a bug in the drivers, and not aeroglass.

look if command also includes VRAM usage when opening it in WPA.exe:

"C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit\xperf.exe" -start PERFSCENARIOS!DWMProfile && timeout -1 && xperf -stop PERFSCENARIOS!DWMProfile DWMTrace.etl

 

look if command also includes VRAM usage when opening it in WPA.exe:

"C:\Program Files (x86)\Windows Kits\8.1\Windows Performance Toolkit\xperf.exe" -start PERFSCENARIOS!DWMProfile && timeout -1 && xperf -stop PERFSCENARIOS!DWMProfile DWMTrace.etl

Made a trace, after about 10 seconds you can see it stopped filling the vram and started filling the normal ram. I was resizing a firefox window. 

https://db.tt/CJfpGuBJ