We didn't observe this during testing, but that doesn't mean there isn't a leak we missed. If it is happening to you and hurting your server, running with -fork 1 should fix it. Even when running a single server, I recommend -fork 1 because, while we fixed every stability issue that we found, -fork should help your server's stability even against issues that we _didn't_ find (yet).
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Daniel Pierce Sent: Wednesday, November 19, 2008 8:25 PM To: [email protected] Subject: [hlds_linux] L4D Memory Leak Hi all. I'm running a single L4D server on a Xen virtualized server. When I start up srcds and wait for a lobby to join it uses 127M ram, but after 12 hours or so it is using about 260M ram and growing. Map changes seem to coincide with the additional memory usage. Anyone else seeing similar issues? _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
