Product version: 2.5.370
OS: Windows XP Pro - SP2
CPU: P4 3.2GHz Northwood
RAM: 1Gb DDR400
-------------------------------
Hi,
The problem im having is, when i turn the computer on, and logon - outpost is using about 3Mb of RAM (brilliant). But when I log off, and I (or someone else) logs on again, outpost.exe is then using around 28Mb, logoff and logon again and its almost at 50Mb.
I've logged off and back on around 10 times, and it's currently using 110,540k!
I thought this could be something with my computer; so I reformatted and just installed Outpost (hence I only have Windows XP and outpost installed) and its still exactly the same.
I paid for Outpost a few months ago, and heard about the fantastic Christmas deal, so if someone can help me sort this high memory usage out then I would purchase another lisense to get lifetime updates - but not when its using a tenth of my RAM.
On Agnitums site, it stipulates that the minimum RAM is 32Mb which i'm finding hard to believe. I'm under the impression that If i logged off/on enough times, i'd run out of memory.
See attached image for memory usage.
Note: I only have the following plugins running: (i) Attachment Quarantine (ii) Attach Detection, and I've limited the log file size to 5Mb to try to resolve this, but it's made no difference.
I don't know of any special term to describe this memory usage pattern - but if you consider it an issue, change Outpost to run in Background mode on startup (via Options/General/Startup). The GUI will not appear unless you open it and memory usage should remain at minimum levels.
Note that Rules Wizard policy cannot be used in Background Mode so Outpost will switch to Block Most policy (though this can be changed - see the Outpost Help for more details on this).
Quote from here in Announcements: Outpost Firewall 2.5 Build 375/374 (http://outpostfirewall.com/forum/showthread.php?t=10164)
+ Memory leak during each logon/logoff
Yes, Memory "leak" is fixed. You can log off and log on without problems. This happened two "beta's" ago and it has been rock solid since (at least for me).
Alright! BTW, you can count on my vote, Mayor!
All see my latest post in : http://www.outpostfirewall.com/forum/showthread.php?t=11966&page=2
You have your words of encouragement -- all will be well, probably with the next release!
Sorry if I used the wrong expression,but I don't know another name for the process,since I'm not that good in English.
I agree that the memory consumption is greatly reduced with this latest version,but the fact still remains that there's 8 MB memory difference of the outpost.exe process usage between leaving the tray icon alone,or maximalise and minimalise it.It simply doesn't go that high anymore,even after several hours.
I know that 8 MB isn't the end of the world,but it's still 35-40 % difference from the memory usage you get after playing with the systray icon.........version 2.1 didn't have that problem,it started right away with approx. 10 MB usage from bootup,and you couldn't reduce the memory consumption with the systray icon......it climbed back to the 10 MB from before.
But what really confuses me is that the total memory usage of my system can differ up to 15 MB by releasing that 8 MB with the systray icon trick.If that's not a memory leak,can you tell me the right name of this problem,please?
Hi,
Can someone confirm whether this memory problem has been fixed in the new release of Outpost 2.5 (375/374) before I reinstall it.
Thanks.
Yes, Memory "leak" is fixed. You can log off and log on without problems. This happened two "beta's" ago and it has been rock solid since (at least for me).
I no longer have to run in background -- can use the GUI! Also, I think that you will find that with the GUI (Normal Mode) that the total memory level has been reduced over that of 2.5 (370). Have fun!
Thanks for confirming that the problems documented in another thread, in which I participated and about which I inquired just yesterday, still exist:
http://www.outpostfirewall.com/forum/showthread.php?t=11966&page=2
It would be nice if the developers would sort of give license holders of Outpost a clue about what's involved in fixing this. My current license expires in February and unless I can find some words of encouragement upon which to hang my hopes......sorry Agnitum, but I won't be sending you any more cash.
I agree that it's better now,but IMHO,it's not totally fixed......latest Outpost still uses 18 MB of Ram,and if you minimalise and maximalise the tray icon,it starts from scratch and builds up to approx 10 MB.....it doesn't go higher,even after a few hours,while you should expect it's going back to the 18 MB from startup ...
The weird thing is,although the difference is 8 MB between the startup and the minimale/maximalise thingy,my system reports a difference of approx 15 MB after that......I tested it with different memory usage monitoring programs.
So I think there's still a memory leak...
So I think there's still a memory leak...A "memory leak" is where a program uses memory but does not release it when finished - resulting in an ever-increasing memory usage. Your figures, with a maximum of 18MB usage, suggest that not only has the problem been fixed but that Outpost's memory usage has been greatly reduced (previous versions used 25-35MB).
 Where's The Advantage In Windows Genuine Advantage?
 Stocks Bounce After S&P Joins Bear Market
|
Memory usage Ballooning!