Hi, I've been able to easily replicate the problem without the need to wait for a week (though doing so will provide better diagnostic results).
If anyone wants to test this follow the instructions below. If you can verify these findings, the more likely Valve will investigate (I'm sure you'll agree that restarting servers every so often due to this is annoying/financially costworthy/bane of your administrative life, right? :). 1. Install a basic installation of Counter-Strike: Source somewhere. Do not install any plugins (such as Mani) as this just complicates the test environment. 2. Create a server.cfg using the following settings: sv_logfile 0 log on 3. Start the server using the following command line: Windows: srcds.exe -console -dev -game cstrike +map de_dust2 +maxplayers 8 Linux/BSD: ./srcds_run -dev -game cstrike +map de_dust2 +maxplayers 8 4. Wait for the server to start (until you see "World triggered: Round_Start" in the console). 5. Take a memory reading: a) On Windows, use Task Manager. Make sure you have the "Mem Usage", "Peak Mem Usage" and "VM Size" columns visible. Look for srcds.exe - record the three figures. b) On Linux/BSD, use 'ps -u' to find the srcds process. You may see several processes with the same name, but as they are threads, they share the same memory space. Note the "VSZ", "RSS" and "%MEM" columns. 6. In the CS:S console, issue the command 'changelevel de_dust2'. 7. Again, wait for the map to load and the game to start (watch for Round_Start again). 8. Take another memory reading. You should see the memory usage increase between 1 and 2 megabytes. 9. Repeat from step 6 and you should see the memory usage increase every time the map is changed. Below are my findings using these steps (starting the server from scratch): Windows: Mem Usage, Peak Mem Usage, VM Size 53,228 - 53,228 - 55,516 54,488 - 56,832 - 56,780 55,720 - 58,540 - 57,944 56,968 - 59,668 - 59,208 57,992 - 60,900 - 60,212 59,304 - 61,840 - 61,532 FreeBSD: %MEM VSZ RSS 25.5 137840 64216 26.0 139080 65516 26.5 140348 66800 27.0 141624 68076 27.5 142888 69340 28.0 144152 70608 To conclude, because the test scenario remains constant and the resulting outcome (a server running dust2) should be the same each time the level is changed (to the same level), there should be no significant and constant changes in memory usage. As an afterthought, I wonder how the memory usage increases if you put 'changelevel de_dust2' in server.cfg... Looking forward to what anyone else discovers. Bart -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steven Hartland Sent: 04 November 2006 18:34 To: [email protected] Subject: Re: [hlds] RE: Memory Leak Bart King wrote: > Indeed, this is a good point. > > However, on my local server (which I use for development work - it > also runs FreeBSD, but that seems to be irrelevant) I have been > running a srcds server, with 8 player slots, accessible from the > Internet (passworded), with 4 bots, changing maps every hour (no > addons). In top, it is showing similar signs of memory leaks after > running for a few days. > > Possible test scenario, I'll have to restart it and monitor it more > closely and see if this is the case. This would be ideal since it > wouldn't rely on real people playing on it. If that does show the leak that is definitely a good reproduction environment for the guys at Valve, nice catch Bart. Steve _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
