Memory consumption, BUG?

[Magic Monkey]

Why OP sometimes use so much memory? Couple of days ago I checked the Task Manager and dropped my mouth wide open when I saw that OP was using 30 megs of my precious RAM?

I just experimented the problem and I found strange things:

When OP is minimized to systray, OP would take more and more memory as the time passes on... and when I double click the icon and the main window comes up, OP takes up even more memory (not much)... BUT when I minimize the window back to systray the memory drops down to about 1-2 megs!!! :confused:

Serious bug?



WinXP, OP 1.0.1511.1038 & filtnt.sys 1.0.228

[root]

Probably has to do with logging. It's a known issue and a new logging system is coming in version 1.1.
Try clearing the logs and see if that doesn't drop the memory usage.

[Magic Monkey]

Originally posted by root
Probably has to do with logging. It's a known issue and a new logging system is coming in version 1.1.
Try clearing the logs and see if that doesn't drop the memory usage.

So do I have to clear the logs just once or do I have to do it regularly?

But if there's a fix in the upcoming version, I don't have to worry about this long... as long as OP won't take all my memory. ;)

[Claude]

hello,
today I noticed also that Outpost used very much memory (up to 44Mbytes). The PC was running but not connected to internet.
After connecting the memory usage drpped down to 3MB.
Then it was using more and more RAM. After opening the outpost window and closing it the usage went down to 3MB.
I think this is a bug and should be corrected in the next version.

[root]

Hi Claude, that is strange. Acting a little different than other memory problems.
The next version,now, is going to be version2, and it has been changed significantly. It is going to have a whole new logging system that will cure most of the memory problems.
I am curious about what you are experiencing. In some ways it sounds like one of Microsofts mystical problems that can't be explaned, but lets check.
Do you use the free or pro version? Also what is the version number? I would like you to see how well you can reproduce the problem and let me know. Also, see if you can see a difference if you highlight all connections, right click and select layout, and uncheck everything except allowed and blocked. That usually saves memory when the logging system is whats eating it up.
I don't understand Outpost using a lot of memory when you are not connected. That means you are on dialup, right?
Any more information on this would help.

[Claude]

Hi Root,
The memory consumption is the same connected or not.
As it was stated before, the memory usage drops down when the main window is opened the iconised.
I am using Outpost free V1.0.1817.1645 on WinXP Home.
Yes I am on dialup via AOL7 (yes I know....)
I chaged the layout leaving unchecked and blocked only.
As I iconised the window the memory usage dropped to 1.5MB.
A few minutes later the mem use is at 5MB.
Now after about 30min. the mem use seems to be stabilized at 8.9MB
Even that is a little too much :(

I'm waiting vor version 2 and will report the changes
As I have enough RAM it doesn't disturb and Outpost is really a nice piece of software.

[root]

Well, if you can live with it, lets wait for ver 2 then.

[Pilgrim]

Claude,

I believe I have a very typical system and so my memory usage should be relatively "normal". I've attached a screenshot of my Task Manager "Processes" with Outpost highlighted so you can see the memory usage I am experiencing. The particulars for my system are: Win XP Home, 512 megs DDRAM, Outpost Pro. I had running at the time, ICQ, Outlook, IE 6.0, Norton AV, ClipCache Plus, SpamWeasel, and Flywheel. The two figures shown for outpost.exe Mem usage: with it sitting in the SystemTray and Peak Mem usage: Main window open.

Jeff

[1ka]

Don't forget, when looking at memory usage using windows task manager, you also need to include the 'VM Size column'. When you minimize outpost then windows swaps out most of the app and you do not see the full memory usage in the 'Memory Usage' column.

[moesasji1975nl]

I am currently using the outpost pro v2.0.226.2921(281) to see how it works.

Most things look good, but I observe the same problem as claude in the above post. Basically the memory being used by outpost increases while outpost is minimized. The longer it is minimized the bigger >44mb.

If I open, memory consumption drops to 1.5mb. (virtual memory then at 12mb)

system : WinXP SP1, 512 mb ram, Browser Mozilla Firebird. (btw, I observe the same under Win2000 SP3)

This really ooks like a bug :hop:
Serious enough to decide not to use this software --> any work arounds available.?

[1ka]

I've noticed this also, and it has been reported in a number of posts. If Outpost is minimized, then VM memory usage continues to increase. Mine was up to 980MB after a hefty Java gaming session at one point.

[DraKKenN]

I'm having this problem too, in different machines.
So that means someone forgot to pay some attention to this well known issue.

I haven't checked different configurations for outpost 2 yet, but it seems worthless, as lots (and clever than me) of people should have done that, with no results..as it seems.

Or maybe someone have a solution...a solution that doesn't involves waiting for Outpost v.3, I mean...

[Pilgrim]

The Developers are aware of this problem with memory consumption. We on the Beta team have reported this and the reports have been acknowledged. It is hoped that the next update will resolve this issue along with several others. With each incremental update, more of the reported bugs will be addressed. The order in which they are addressed is determined by the severity of the bug. Where this one ranks on the list, I am do not know.


Jeff

[moesasji1975nl]

I hope it is high on the list and let me explain why.

The major reason for me to give outpost a try is that it has similar options as NIS2003. And norton noticably slows down my systems/is a big resource consumer. The reason to use outpost for me is that it would be less demanding on system resources, while still offering things like ad-block integrated in the firewall.

Well bad luck at the moment.
1) Memory use increases continuously as posted above.
2) One of my test-systems is in a big (I guess >10000 computers) shared LAN. There the problems with the logfiles is a big problem. Because the logfile gets so big, I can not look at it and therefore not clean it. This makes the system grind to a halt within hours.
--> only remedy is marking the logfile for deletion and reboot. (not a good option...)

My conclusion would be not to switch to outpost for these reasons.....and I will stick with NIS2003 unless these problems are quickly resolved. I guess similar reasoning will apply for a lot of people?

[Paranoid2000]

Originally posted by moesasji1975nl
I guess similar reasoning will apply for a lot of people? Erm, not likely - Outpost is a personal firewall intended for use on a single PC or a small home network. Your mention of a 10,000 node LAN suggests your "home" is not typical of most users.

As for workarounds, I suggest you visit the V2 FAQ - there are 2 threads there dealing with this - Disabling Logging (http://www.outpostfirewall.com/forum/showthread.php?s=&threadid=7392) and How to troubleshoot high CPU usage problem? (http://www.outpostfirewall.com/forum/showthread.php?s=&threadid=7570) Keeping the main OP window open all the time (which seems to keep usage constant) should qualify as a third.

[moesasji1975nl]

In the case of logging problems. My apartment in is located on a university terain. Every computer (also home computers) are directly connected to the university network. I agree this will not be the case for many people.

But the problem with the memory consumption is in my opinion not related to this. I had already seen the post howto disable logging and I renamed the file "op_data.dll". This however does not appear to affect the memory consumption. And this is my main problem with outpost at the moment.

What I meant to say that for users switching away from NIS2003 it is important that a firewall uses few resources/doesn't affect systemspeed and is compatible with your OS. (this is the reason why I would want to replace NIS2003, not for the features as they are comparable)

[zetsu]

Outpost v2 is using 144mb of RAM. Is this normal?
While the first versioin is consuming only 1-3 mb.

[Dmut]

Hello zetsu. could you describe you network environment and usual tasks?
my experience of using both versions for a long time telling me, that v2 is consuming memory much more slower than v1, in the same environment, of course.

[zetsu]

Originally posted by Dmut
Hello zetsu. could you describe you network environment and usual tasks?
my experience of using both versions for a long time telling me, that v2 is consuming memory much more slower than v1, in the same environment, of course.

I've got some services that make a lot of connections (and outpost accepted log entries too) each minute. I've temporarily disabled them and outpost is using only ~7mb ram now.

[DraKKenN]

Keeping Outpost window open doesn't help a bit. Even having outpost running & disabled doesn't solve the problem.

Memory increases every time a program opens and/or closes, and with ech in/out connection, enabled, disabled, active window, in system tray...whatever.

Sometimes increases memory in a few K's, sometimes in a few Mb's...and it never reaches stability: in my case,using 750mb, sometimes consumes up to 500 mb...a little problem, as you may notice :)

So...at least I'd like to know wich priority rating has this ¿ bug ?, just to know how much more I'd have to wait until I could use an usable Outpost v.2