gwes.exe memory usage
 

I just updated to the Verizon 6.5 stock rom and the memory usage for gwes.exe is very high, around 31MB usually. It starts out about 24MB but slowly creeps upwards. Anyone else experiencing this?

Re: gwes.exe memory usage
 

From what I understand, it is the subsystem that runs the drivers, manages windows...

The more you use the device, the more memory it would need. Mine is typically around 46MB after a couple of hours of use.

Re: gwes.exe memory usage
 

Can anyone explain what exactly this thing is doing? I am currently using EnergyROM Leo January 14 and after 14 hours of use GWES.exe is using 46MB. When I close everything including manila it only drops to 44MB. Does this process have memory leaks? I have never had a WM 6.5 ROM where GWES.exe does not grow to ridiculous sizes.

Why does it not release memory? I think 6.5 is inherently flawed as this is even a problem on official ROMs. I have been looking for an answer to this every since I first tried 6.5 and no one has ever given a good explanation. Why would it need more memory the more you use the device? That only points to memory leak.

What is hilarious is it seems GWES has always been problematic. Look at this ancient thread
forum.brighthand.com/showthread.php?t=211179
They are complaining that it is using 5.25MB and grows to 6.1MB. That was a significant chunk when devices has 64MB RAM. Its the same problem though, it cache's things and never lets go! Weired that it has grown to 25MB at startup even though that device used a 640x480 screen meaning the graphics were the same size. Is there a way to lower the maximum cache somewhere? I will give up a few milliseconds loading time to make it so I don't have to soft reset every day.

Re: gwes.exe memory usage
 

sorry to bump this thread, but im encountering the same problem so was wondering if anyone has come up with a solution yet?

Re: gwes.exe memory usage
 

There is no "solution"

gwes.exe is one of the main system processes used by WinMo. As stated above, the more you use your phone, the more the usage by this process will creep up. It's hard coded into the kernel to be that way

The only way to dump the process back to a low level again is to soft reset