Memory Leaks?

[Prez Bush 1]

I run a dedicated server on Win2k Server with 512mb ram and a T3 connection. Win2k is as patched as a Microsoft OS can get but I find that the server slowly grabs more memory until it quits running. This takes about 2 or 3 days of 24/7 running. When I kill the window to get it to restart (running in a .bat, perm loop) it kills the window but not the process as seen in task manager. That process starts out using ~24mb of ram and has over 100mb when I force kill the process. After forcing the process down, I can restart the dedicated server engine and the whole loop begins again. I have tried rebooting the whole server too. There isn't anything running on this server but OFP.

On another note, why can't people join an in progress game like most other first person shooters out there? (with exception of Rainbow Sick)

[sergeant rock 3]

I have experienced the same problem on my W2k server.  I have about 396 MB RAM that slowly gets chewed away until I either kill the process or the server locks up.  I've see dedicated server 1.3 chew up over 300 megs of RAM.  I've also seen the issue where the window is killed but the OS holds onto the process.  I hope BIS can address these leaks.....

[Mister Frag 0]

Yes, there are still memory leaks in OFP, both the normal game executable, and the dedicated server. The developers are aware of this, and have promised to address this problem.

Joining a game in progress is not possible at this time, and while a TON of people have requested this feature, the developers have stated that it doesn't fit the current engine's design, or the intended style of play. Whether this will ever find its way into OFP is doubtful.

Regarding the problem with killing the server, while the window is owned by the process, just closing the window isn't the same as terminating the process.

[Prez Bush 1]

I understand that terminating the window isn't the same as killing the process but the two usually go hand in hand. If I start dedicated server and then close the window, the process goes. If I wait two days and 200mb of ram later, the process hangs.

Anyone have any ideas on automatically terminating the server and restarting it on a daily basis? That would be a sufficient workaround ( I think, assuming the process dies) until the leak issue is addressed.

[unholy chosen one 1]

prez how familiar are you with win2k server? are you an admin? im a mcse and can help you with this but it helps you have some idea of the procedures i need you to go thru.(it will sound complicated but its not near as bad as it sounds)

the problem with memory really isnt ofp its partly the way the server is set up and partly a problem microsft has with all its o/s's

(Edited by unholy chosen one at 3:14 pm on Nov. 21, 2001)

[Angry Radish 0]

Another helful thing you can do is to run the ofp commandline as a service using firedeamon, or similar program, and aslo to disable dr.watson logging in the registry, which will at least save you time dumping logfiles.

I had the same problem with the task not really ending, and having to force it to end, but stopping and restarting the sevice has saved me from having to go through that hassle more often.

Just my 2C

[Mister Frag 0]

</span><table border="0" align="center" width="95%" cellpadding="3" cellspacing="1"><tr><td>Quote </td></tr><tr><td id="QUOTE">Quote: from Prez Bush on 9:37 pm on Nov. 21, 2001

I understand that terminating the window isn't the same as killing the process but the two usually go hand in hand.  If I start dedicated server and then close the window, the process goes.  If I wait two days and 200mb of ram later, the process hangs.  

Anyone have any ideas on automatically terminating the server and restarting it on a daily basis?  That would be a sufficient workaround ( I think, assuming the process dies) until the leak issue is addressed.  

<span id='postcolor'>

That's easy -- you can use the Task Scheduler to do that. Go to Control Panel -> Scheduled Tasks and add a task for the server. In the Settings tab, you can have the task terminated automatically if it is still running after a specified time.

This way, you could launch a new OFP server at say 7AM (I hope you guys are all done by then!), and kill it 23 hours and 59 minutes later, just in time for the next instance to be launched.

[OhHell 0]

Prez Bush:

If you run the OFP server as a service you can then use the scheduler to close the server down and restart it with the net stop and start commands at a certain time.

Use Firedaemon to run it as a service