FlightControl Posted October 25, 2014 Posted October 25, 2014 I've made the attached mission, for 1,5 years now. This mission used to run really smoothly after al the tweaking and fixed that i did during the past months, but since the last updates of DCS world, it seems that at certain unidentified events, the server gets a memory leak, and the server is hanging. When the error situation occurs: 1. the server hangs (no user input possible), and the memory consumption of the DCS process goes up and up and up, but slowly... Even to about 8 gigbytes, i've seen even 16GB of consumption also when i leave this process. 2. Clients logged onto the server won't notice a thing. But they will experience severe lags, and also sometimes, they cannot switch from client. 3. Clients trying to load the mission and logging into the mission, are simply hanging for a while, and slowly they can login also... I can only simulate the errors when there are client machines onto the server. When i leave the server running and nobody is logged into the server, it runs smoothly without problems... what to do??? Please help guys, i am searching and searching and searching... This is a very complicated mission. I've debugged all of my code, but cannot find the process that might be spinning in an infinite loop or something. What is going on???? http://forums.eagle.ru/showthread.php?t=124741 kind regards, Sven [TABLE][sIGPIC][/sIGPIC]| Join MOOSE community on: DISCORD :thumbup: Website of the MOOSE LUA Framework. MOOSE framework Downloads. Check out Example Missions to try out and learn. MOOSE YouTube Channel for live demonstrations and tutorials. [/TABLE]
FlightControl Posted October 25, 2014 Author Posted October 25, 2014 Reverted to DCS World version 1.2.10.32095 on the server... The server is running now for about 1 hour without any issues yet. So, if the revert was the solution (short term), then for sure the error is related to DCS World, and the error was introduced in later versions (1.2.10.32275, 1.2.10.32582). I'll confirm today. Sven [TABLE][sIGPIC][/sIGPIC]| Join MOOSE community on: DISCORD :thumbup: Website of the MOOSE LUA Framework. MOOSE framework Downloads. Check out Example Missions to try out and learn. MOOSE YouTube Channel for live demonstrations and tutorials. [/TABLE]
johnv2pt0 Posted October 25, 2014 Posted October 25, 2014 I'm interested in what you find. My server has had unexplained crashes and odd behavior recently as well.
FlightControl Posted October 25, 2014 Author Posted October 25, 2014 (edited) Johnv2pr0, Thanks for your reply. To get your server stable, revert back to an older version of dcs world by opening a command prompt. Navigate to your program files directory\eagle dynamics\dcs world\bin Type in that directory: Dcs_updater update 1.2.10.32095 This will revert your server to the release that I think its stable. To identify the issues you're facing Run your missions in the latest release and pls communicate your findings also. For debugging purposes of my mission, I have put a scheduled function that is logging up to the millisecond a timestamp. Because when the memory leak starts, there is no further logging. Then I can try to find the event in the event log that caused the issue. Maybe you can try this also... Sven Edited October 25, 2014 by FlightControl [TABLE][sIGPIC][/sIGPIC]| Join MOOSE community on: DISCORD :thumbup: Website of the MOOSE LUA Framework. MOOSE framework Downloads. Check out Example Missions to try out and learn. MOOSE YouTube Channel for live demonstrations and tutorials. [/TABLE]
FlightControl Posted November 5, 2014 Author Posted November 5, 2014 (edited) I'm interested in what you find. My server has had unexplained crashes and odd behavior recently as well. Found the root cause .... It has to do with the spawning function Coalition.CreateObject... When you have in your structure to be spawned a ground unit defined... And you have the field "visible" = true and lateActivation = "false" then the ground unit will spawn after the call and in single player or with only one client logged on, everything will seem to go like normal. However, ... when you have more than 1 client logged onto the server, and that function will be called, you notice that immediately (a few seconds after), that server starts to hang... Logged on clients however will not notice much. The mission will continue, but all further scheduled calls will stop to happen. So, once i detected this after my severe testing, i have changed this little bug in my logic. I Always Ensure that "visible" = false in my logic. And now my missions are running like a train. My server is not hanging anymore, and units are spawning perfectly. Sven Edited November 8, 2014 by FlightControl [TABLE][sIGPIC][/sIGPIC]| Join MOOSE community on: DISCORD :thumbup: Website of the MOOSE LUA Framework. MOOSE framework Downloads. Check out Example Missions to try out and learn. MOOSE YouTube Channel for live demonstrations and tutorials. [/TABLE]
ajax Posted November 5, 2014 Posted November 5, 2014 Nice detective work, Sven! I'll modify my scripts and then see if the server stability improves. Thanks!
FlightControl Posted November 8, 2014 Author Posted November 8, 2014 Let me know if it helped... [TABLE][sIGPIC][/sIGPIC]| Join MOOSE community on: DISCORD :thumbup: Website of the MOOSE LUA Framework. MOOSE framework Downloads. Check out Example Missions to try out and learn. MOOSE YouTube Channel for live demonstrations and tutorials. [/TABLE]
Recommended Posts