Memory Usage Does not Decrease Unless Manually Minimized...?
Posted: Sat Jun 18, 2011 3:00 pm
Hi, Bill! On the thinclient I am using, I've decided to scrap Explorer.exe and use the Opera web browser as my shell. Ascendis is to run in the background, with the YAC Listener picking up incoming calls and displaying them full screen.
When minimized to the system tray in Windows while using Explorer.exe as the Windows shell, Ascendis uses a paltry amount of memory, maybe 3.5 megs. When a call comes in, the memory increases, but as soon as the caller information disappears, the memory drops right back down. However, when I switched to using Opera.exe as the Windows shell, the memory climbs to over 12 megs, and then, instead of dropping back down once the caller information disappears, it stays high.
Each subsequent call bumps the memory a little bit higher (12.580 megs, 12.632 megs, 12.644 megs etc.) and it does not fall back down like it does under the default Windows shell.
I am using the latest version of Ascendis, and I am starting Ascendis via
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
under "Userinit".
1) Why is it rising each time?
2) Why isn't it falling back down each time?
~Bryan
EDIT: 6/18/11 9:21 P.M. EDT
I tried a few other experiments. This time, I left Explorer.exe running, and noticed that unless I minimize the program manually, Ascendis does not relinquish the RAM back to the system. For example, if I tell it to run in the system tray and issue a YAC test call, the information pops up on the client, and the memory usage expands to about 12 megs. After the notification window goes away, the memory usage stays there. When I click on the program in the system tray to bring it to the foreground/maximize it and then deliberately minimize it, then the memory usage is returned, and Task Manager shows a reduction back to a meg or so (which is awesome).
When minimized to the system tray in Windows while using Explorer.exe as the Windows shell, Ascendis uses a paltry amount of memory, maybe 3.5 megs. When a call comes in, the memory increases, but as soon as the caller information disappears, the memory drops right back down. However, when I switched to using Opera.exe as the Windows shell, the memory climbs to over 12 megs, and then, instead of dropping back down once the caller information disappears, it stays high.
Each subsequent call bumps the memory a little bit higher (12.580 megs, 12.632 megs, 12.644 megs etc.) and it does not fall back down like it does under the default Windows shell.
I am using the latest version of Ascendis, and I am starting Ascendis via
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
under "Userinit".
1) Why is it rising each time?
2) Why isn't it falling back down each time?
~Bryan
EDIT: 6/18/11 9:21 P.M. EDT
I tried a few other experiments. This time, I left Explorer.exe running, and noticed that unless I minimize the program manually, Ascendis does not relinquish the RAM back to the system. For example, if I tell it to run in the system tray and issue a YAC test call, the information pops up on the client, and the memory usage expands to about 12 megs. After the notification window goes away, the memory usage stays there. When I click on the program in the system tray to bring it to the foreground/maximize it and then deliberately minimize it, then the memory usage is returned, and Task Manager shows a reduction back to a meg or so (which is awesome).