M
Mikolaj
Hello,
I have found the following situation with MSAS Beta 1, that repeats every
time I check.
Just after loading GIANTAntiSpywareMain.exe (shouldn't it be
MSAntiSpywareMain.exe? ) it consumes about 12,5MB of RAM. Without
starting any system scan and without running any function or tool, just
doing "walkthroug" through Options/Settings and Tools menu, just taking a
look at settings, agents and so on, all the time it increases memory usage
by this module. After several mouse clicks and few minutes of such actions,
from 12,5MB this application consumes over 29MB of RAM. And I stopped here
(without further investigation).
After closing the application and opening it once more, again it starts
with memory usage at level 12,5MB.
System:
Windows XP Home Edition Polish with SP2 and all latest updates, 1GB RAM
MSAS:
Microsoft AntiSpyware Version: 1.0.509
Spyware Definition Version: 5705 (2005-04-09 00:51:26)
(I can provide Task Manager screenshots with memory levels, if needed.)
The question is - is this some kind of problem/bug in the application?
Kind regards
Mikolaj Kaminski
MS-MVP, Poland
I have found the following situation with MSAS Beta 1, that repeats every
time I check.
Just after loading GIANTAntiSpywareMain.exe (shouldn't it be
MSAntiSpywareMain.exe? ) it consumes about 12,5MB of RAM. Without
starting any system scan and without running any function or tool, just
doing "walkthroug" through Options/Settings and Tools menu, just taking a
look at settings, agents and so on, all the time it increases memory usage
by this module. After several mouse clicks and few minutes of such actions,
from 12,5MB this application consumes over 29MB of RAM. And I stopped here
(without further investigation).
After closing the application and opening it once more, again it starts
with memory usage at level 12,5MB.
System:
Windows XP Home Edition Polish with SP2 and all latest updates, 1GB RAM
MSAS:
Microsoft AntiSpyware Version: 1.0.509
Spyware Definition Version: 5705 (2005-04-09 00:51:26)
(I can provide Task Manager screenshots with memory levels, if needed.)
The question is - is this some kind of problem/bug in the application?
Kind regards
Mikolaj Kaminski
MS-MVP, Poland