¿¿ Memory Leaks ??

[nicedreams242]

My server maintains it memory usage with all my other services running

Once I start my TS server, it slowly gobbles up the memory being used, with less and less free the longer I leave it running. Even stopping the server seems to not free up the memory.

So issuing a reboot, reset the memory, obviously. Don't run the TS for a few days, and the memory seems to be stable. Turn on the TS again, and WOW gobble gobble gobble again.

I know this is RC2 so maybe this is an outstanding issue.
Anyone else noticing this problem?

[nicedreams242]

(BUMP) Does no one pay attention to their memory usage? :(

[MMmmGood]

This issue also effects the Windows TS server, I have made a post there with multiple replies from others with no response/fix from TS.

[nicedreams242]

Thx MMmmm Good at least someone is watching their memory.

[Brain]

I don't experience any memory leaks. However my server is fairly small (2x32 slots) and rarely used (about three to four times per week, 5 to 6 people on an evening).

[nicedreams242]

My server at most has 8 slots used at a time.

And still memory just wears away in to neverland.

[Brain]

What are the first 5 lines of your top output?

[nicedreams242]

top - 12:54:46 up 16 days, 20:29, 1 user, load average: 0.00, 0.00, 0.00
Tasks: 67 total, 1 running, 66 sleeping, 0 stopped, 0 zombie
Cpu(s): 0.0% user, 1.0% system, 0.0% nice, 99.0% idle
Mem: 904484k total, 862560k used, 41924k free, 95020k buffers
Swap: 2097136k total, 0k used, 2097136k free, 532400k cached


The part that bothers me is the 41924k free keeps going down and down.

[Brain]

That's perfectly normal. Linux uses the remaining free memory for caching.
By the way, do you happen to have 1GB RAM on that machine? If so you might want to set CONFIG_HIGHMEM4G=y in your kernel config (and recompile). That should give you an additional 100MB.

[Label2021]

Yes that is normal, let the server runs for weeks if you can, it will say it takes up all of your memory. But you shouldnt ever notice your PC ever act as if it only has 4-5 MB of memory left, because if it did, you wouldnt even really be able to successfully send commands too well. As Brain said, it is just used for caching, and isn't any performance decrease to it at all.



-LabeL-

[nicedreams242]

Thank you both for the explanation. I was begining to worry, but I guess that makes sense. I just usually do not notice anything else doing that with the memory, but you are right in that I don't notice a performance decrease.

Yeah Brian I do have 1GB of RAM and was wondering the 900 ish number sounded kinda strange.

Thanks Again

[Peter]

Maybe not very teamspeak related, but for the 1 GB systems it is not advised to use highmem, since the resulting overhead is apparently not worth the extra RAM, see: http://kerneltrap.org/node/2450


Should I enable CONFIG_HIGHMEM for my 1 GB RAM system?



It is advised to not enable CONFIG_HIGHMEM in the kernel to utilize
the extra 128 MB you get for your 1 GB RAM system. I/O Devices cannot
directly address high memory from PCI space, so bounce buffers have to
be used. Plus the virtual memory management and paging costs come with
extra mappings. For details on bounce buffers, refer to Mel Gorman's
documentation (link below).


The ck patchset had a special patch though that changed the split rate to just allow 1 GB of RAM to be addressed (without the problems described above), if you care I would advise using that - but be warned, it messed up my valgrind.