Big memory leak on linux headless build.

Hello,

I am building my masterServer for my multiplayer game on linux with headless mode.
Everything goes well the first few hours, i monitor with htop, my MasterServer is at 3.5-4% of the memory used.
Then after a few hours, it is at 63% wich cause the MasterServer to not work properly anymore.
I removed from my build everything i heard could cause a leak: camera, canvas, OnGUI(), update() etc...

Did you hear something similar, what do you think i could ?
Any suggestion is welcome.

thanks
here is the game:
http://www.adversator.com/

 

@natosha-bard
I know a few persons that have the same problem as me.
I can't be the only on this forum that is hosting his online game on a linux VPS.
Could you lend me a hand please ?

 

one of my panel was attached to LoadingManager Script, where following update code was written. As you can see Text was appended wrongly += with loading string over and over, i have memory leak in headless mode. Although this panel is never opened in headless mode but this is referenced in main canvas. To find out, i have set break point in all update methods in the solution and by the help of Allah i could find out this after several months. I am using unity 2019.1 editor with let me debug all the scripts also unity network codes.

Code (CSharp):

1. void Update()
2.     {
3.         if (gameObject != null && gameObject.GetComponent<Text>() != null && gameObject.activeSelf)
4.         {
5.             if (DateTime.Now.Millisecond > 500)
6.             {
7.                 gameObject.GetComponent<Text>().text += "Loading....";
8.             }
9.  
10.         }
11.     }

Long story short: check all of your update methods closely. Remove string appends or Ressourse.load() from update method.

 

Has anyone managed to fix the problem? Still relevant as of 2019.4.13f1

 

Tracking down a memory leak in a 2018.4.31f1 game's headless Linux build. Let me know if any tips on common causes (theory right now is something around Resources.Load of our levels, but haven't narrowed it down yet).

 

That's an old thread, I don't remember well how I managed to get ride of the leak, I think it was related to a InvokeRepeating.
So i removed all the InvokeRepeating and replaced them with loops in Update.
"I think" it did the trick for me, but i changed so many things at this time, that i am not even sure.
But as ShantuApps mentioned above, it can be your code too.
My very first step now, would be, to make a build on Windows and monitor it to see if the leak happens on Windows too.
Launching the server in Editor to check with profiler could be good too.
Hope it helps a little.