• Hey Guest, we're evolving the future of TeaSpeak.
    You're invited to join the discussion here!

Completed Memory leak solved?

yamano

TeaSpeak Team
Staff member
TeaTeam
@Kevinos lucky guy xD
I just saw three guys saying "The memory problem is solved"
(You, a centos 7 guy and some other guy with debian 8 x32),
so 99% are still with ram consumption problems..

All my installations and the people that i know are with memory consumption problems.
(All using Debian 9 x64)

Maybe it was a Debian x64 problem, i do not know...
 
Last edited:

szkuta

Well-known member
memory leak fixed in centos7 too
if users left instance memory falls down
but anyways there is a big ram usage for teaspeak at all^^
 

yamano

TeaSpeak Team
Staff member
TeaTeam
memory leak fixed in centos7 too
if users left instance memory falls down
but anyways there is a big ram usage for teaspeak at all^^
I'm really sad about mine installation.
In Debian 9 x64 dont show to be solved at all..
You forgot to say the bits... 32 or 64bits?
 

szkuta

Well-known member
64bit version of latest centos 7 release
its a high ram usage at all . . . thats for sure
but if users leave instance (servers) memory falls down to at least ~30-50MB with 2-5 users on instance i think^^
 

yamano

TeaSpeak Team
Staff member
TeaTeam
"but if users leave instance (servers) memory falls down to at least ~30-50MB with 2-5 users on instance i think^^"

I do not care that teaserver uses a lot of ram,
as long as the consumption stays stable and goes down whenever the users are not online.
Something that does not happen!!
Consumption always increases even without online users...
I'm getting tired of this problem :/

so, for what i see, Centos 7 x64 and Debian 8 x32 are the systems where "aparently" the ram problem seems to be solved.
I've never tested teaspeak in those systems.
 

szkuta

Well-known member
okay with "CentOS Linux release 7.5.1804 (Core) 64bit" i dont have the problem
maybe you give it a try and test with CentOS Linux release 7.5.1804 (Core)?
 

WolverinDEV

TeaSpeak Team
Staff member
Administrator
Well may post the log and if present crash dumps :)

A version history could be found here repo.teaspeak.de :)
 

WolverinDEV

TeaSpeak Team
Staff member
Administrator
There isn't a "real" fex because Teaspeak hasn't a memory leak.
It may be possible that you still not use jemalloc as memory allocator. And as I said if you could send me the meminfo output I can give you a little it more detail.