HELP! Zero-K (using Chobby) unusable in Linux

I am rather frustrated at the moment as Zero-K now consistently grinds my computer to a halt, and I have to push the reset button, under linux on the second loading of the game.

Don't know if this is relevant:

Jan 02 19:19:19 light0 menulibre-new-launcher.desktop[23698]: Zero-K.exe Error: 0 : Error reading version list from http://tadrd.repo.springrts.com: System.Net.WebException: Error getting response stream (ReadDo
Jan 02 19:19:19 light0 menulibre-new-launcher.desktop[23698]: at System.Net.WebConnection.ReadDone (System.IAsyncResult result) [0x00000] in <2fef7234205a4a009fe5995569c314ee>:0
Jan 02 19:19:19 light0 menulibre-new-launcher.desktop[23698]: at System.Net.Sockets.SocketAsyncResult+<>c__DisplayClass27_0.<Complete>b__0 (System.Object _) [0x00000] in <2fef7234205a4a009fe5995569c314ee>:0
Jan 02 19:19:19 light0 menulibre-new-launcher.desktop[23698]: at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem () [0x00000] in <73ee1b14c2fa4d61b481096ff3d8d6d
Jan 02 19:19:19 light0 menulibre-new-launcher.desktop[23698]: at System.Threading.ThreadPoolWorkQueue.Dispatch () [0x00000] in <73ee1b14c2fa4d61b481096ff3d8d6d7>:0
Jan 02 19:19:19 light0 menulibre-new-launcher.desktop[23698]: at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback () [0x00000] in <73ee1b14c2fa4d61b481096ff3d8d6d7>:0
Jan 02 19:19:19 light0 menulibre-new-launcher.desktop[23698]: at System.Net.WebConnection.HandleError (System.Net.WebExceptionStatus st, System.Exception e, System.String where) [0x0003b] in <2fef7234205a4a009
Jan 02 19:19:19 light0 menulibre-new-launcher.desktop[23698]: --- End of inner exception stack trace ---
Jan 02 19:19:19 light0 menulibre-new-launcher.desktop[23698]: at System.Net.HttpWebRequest.EndGetResponse (System.IAsyncResult asyncResult) [0x00058] in <2fef7234205a4a009fe5995569c314ee>:0
Jan 02 19:19:19 light0 menulibre-new-launcher.desktop[23698]: at System.Net.HttpWebRequest.GetResponse () [0x0000e] in <2fef7234205a4a009fe5995569c314ee>:0
Jan 02 19:19:19 light0 menulibre-new-launcher.desktop[23698]: at ZkData.Utils.DownloadFile (System.String url, System.Nullable`1[T] ifModifiedSince) [0x000c7] in <fc637dbccd864faab05afa4f81da8d82>:0
Jan 02 19:19:19 light0 menulibre-new-launcher.desktop[23698]: at PlasmaDownloader.Packages.PackageDownloader+Repository+<>c__DisplayClass16_0.<Refresh>b__0 () [0x0002b] in <fc637dbccd864faab05afa4f81da8d82>:0

Window's task manager shows 1.2gb - 2gb on various battles, never seen over 2gb in win...
But this is probably because chobby still downloads 32bit spring on windows, does it?
A year ago or so I remember manually checking 64bit build for windows - it worked perfectly and afaik I even had slightly higher fps

Just did a small test on Linux:

after starting chobby spring already needs 1.5GB
after joining a 11v11 game (5 minutes into the game) the memory consumption is at 6GB
after leaving the game and returning to lobby (via lobby -> leave): still at 6GB
after rejoining the same game: 8GB
after rejoining the same game a third time: 10GB
...

Just tried using flobby-git Archlinux package and I see zero issues.

The engine is currently leaking tons of memory, I have noticed that too. I just couldn't be bothered to do a bugreport yet.

About the 5GB on Linux vs 1.5GB on Windows:
64-bit spring default to using the fairly new LuaMemPool (adds ~2.3GB mem usage for me) which seem to be an attempt to avoid OOM issues reported by zk players, see https://springrts.com/phpbb/viewtopic.php?p=582590#p582590 .
Also, 32-bit spring will use less memory than 64-bit spring even with this mempool disabled (UseLuaMemPools = 0).

I find it a bit odd that the zk OOM issues can be resolved by this since the mempool is likely disabled for all windows zk players running 32-bit spring, perhaps someone(hokomoko?) can explain this though.

To be clear here, is the issue that Chobby is setting up a 64-bit instance of spring, which is failing, whereas flobby is setting up a 32-bit instance of spring, which is not failing? If so, why does flobby get a 32-bit rather than 64-bit version? If not, then why is running Zero-K under Chobby but not flobby failing?

I have also had problems with colossal huge amount of ram being used, 8 GB in computer not enough.

Did some testing now while monitoring ram usage via top (ssh app on phone).
~1,5 gigabyte ram used just entering the lobby.
Spectating some online speedmetal, fast forward 14 minutes into game, < 3.5 gigabyte ram used.
Then a new 2 player game on same map, with few units. Same amount of ram.
Then some single player, about the same gigabytes used.
And finally a chicken game started at over 3 gigabyte and ended below 3 somehow after a while.

So whatever made it use super large amount of ram before seems to be solved. (?)

Just noticed that flobby appears to be obtaining and presumably using the 64-bit version of spring:

spring_{maintenance}104.0.1-92-g4409317_minimal-portable-linux64-static.7z

I copied over springsettings.cfg from Chobby to flobby so it cannot be that. What other files should I be looking at?

Who is having 8 GB of ram in 2018? -facepalm-
Upgrade this shit!