I am a long-time user of Super Antispyware, and I am now having the exact same issue as The Scorpion. Same general system limitations -- 512MB RAM, no graphics RAM, single-core PEntium P4M processor on an older (2005) Winbook laptop.
SAS Core and the Updater max out RAM and Paging Files. Windows XP Pro SP3 (32-bit), fully patched, freezes and I have to use the hardware reset button.
The past two SAS program versions have been doing this.
Turned Comodo Firewall down to Training Mode for Firewall and Defense+.
SAS won't even start up in Safe Mode, but the Tray Icon (the "Bug") is present.
When installing, the Installer was able to update to the latest definitions, but when installed, the program is not updating. Rather, memory usage explodes and the hard drive thrashes.
This is definitely a classic Memory Leak, somewhere in the SAS Utilities or the SAS Updater parts of the installed SAS program. Especially at the stage when the Core Definitions are being processed (and written to a protected directory).
The Technician's Edition (SAS Portable) downloads and runs scans just fine, but I really want to install SAS permanently on this laptop.
I have no problems whatsoever with SAS installed on my recent (2010) dual-core (Intel Core i-5) Toshiba Satellite laptop with 4GB system RAM and NVidia/Intel dual-mode graphics. This is under 64-bit Windows 7 Home Premium, SP1, fully patched.
Clearly, the difference is mainly in the Operating System Version and in the available System Resources, especially RAM. Perhaps also a difference in the 64-bit SAS mode vs. the 32-bit mode.
While the issue is being looked into, I can continue to use the SAS Portable version on the Winbook. It's a bit of a bother to download a fresh copy every time I need to scan that laptop, but the scans seem to be of equal quality to the installed SAS program, except that I cannot build up a list of Allowed Files, such as the Nir Sofer Utilities which are always flagged as Hack Tools.
Overall, I was completely satisfied with SAS until these updates, and have continued to recommend this excellent antispyware program. I would just like for this Memory Leak issue to be resolved.
To clarify what I wrote above, I think the leak is happening when the Updater is processing the Core Definitions (and trying to write to the protected SAS directory associated with its Definitions). But there are other times when SAS and SAS Core are consuming large amounts of RAM on the Winbook.
I was involved in an exchange with SAS technical staff several years ago when a very simiilar issue was happening. Only at that time, the memory leak was so severe as to cause a Blue Screen of Death in Windows XP. It seemed at the time that the SAS Updater was failing to write to its own protected directory for some reason. The cause was found to involve at least one aspect of the Zone Alarm Firewall (similar to the Kaspersky antivirus engine). I no longer use Zone Alarm, and Comodo should have little in common with the old Kaspersky engine. And, I have reinstalled Windows XP on the Wnbook since then.
I hope some of these details help track down the present memory leak issue.