yep, you have to restart an app to recover leaked memory. Otherwise it wouldn't be leaked memory. Plus it's only using up pagefile/swap space anyways, so it's not a huge concern unless you're running out of pagefile/swap space, even though it would be better if the leaks were taken care of and didn't happen at all.
On Sun, 16 Jan 2005 18:19:10 -0600, hondaman <[EMAIL PROTECTED]> wrote: > I believe the exec banned_* commands in server.cfg are what is causing > this "leak" > > The Fool wrote: > > > Leaked memory can not be "taken back". > > Leak(in general) = memory is 'locked' by the running application, but it > > never used by it anyway (un-released objects because of silly > > cross-references, etc, etc). Leaking is a bug. The only possible > > workaround > > is to stop and restart the leaking application. > > > > > > > >> I notice that srcds_amd continually has been using more and more ram (up > >> to 183mb) over time, even though there aren't always players on the > >> server. I think this is due to memory leaks as noted in prior mailing > >> posts, but I'm wondering if anyone knows of a way to recover this leaked > >> memory. Or is the only feasible option to restart the daemon? > > > > > > > > _______________________________________________ > > 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 > -- Clayton Macleod _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds_linux
