2025-07-31 02:28 CEST

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0005861Spring engineLinuxpublic2019-01-22 19:39
Reportermeep 
Assigned ToKloot 
PrioritynormalSeveritymajorReproducibilityalways
StatusresolvedResolutionfixed 
Product Version 
Target VersionFixed in Version 
Summary0005861: spring + chobby + linux memory consumption grows considerably after each game
DescriptionWhen using Zero-K + chobby on Linux the memory consumption of the spring process grows each time you start a new game (without restarting chobby). With UseLuaMemPools set to the default value (which I suppose is 1?) each game requires an additional 2GB of RAM, which seems slightly excessive.

chobby with "UseLuaMemPools = 0":
start: 1.5GB
1st game: 3GB
2nd game: 3.25GB
3rd game: 3.5GB

chobby with default value ("UseLuaMemPools = 1"?):
start: 1.5GB
1st game: 6GB
2nd game: 8GB
3rd game: 10GB
Steps To Reproduce- start Zero-K (mono Zero-K.exe)
- load attached replay and wait until game is started
- leave game and return to lobby
- load attached replay again and wait until game is started
- ...
Additional Informationspring: 104.0.1-92-g4409317 (64 bit)
Zero-K: 1.5.12.5
TagsNo tags attached.
Checked infolog.txt for Errors
Attached Files

-Relationships
+Relationships

-Notes

~0019678

Kloot (developer)

Fix 3a14eb31f1b03f993161ef9aa4782f5cb0a03ac6 committed to develop branch: fix 0005861, repo: spring changeset id: 11291

~0019679

Kloot (developer)

Fix 0ecf03285ab400bbd02f96ac2457b7abb7c4f591 committed to maintenance branch: fix 0005861, repo: spring changeset id: 11293
+Notes

-Issue History
Date Modified Username Field Change
2018-01-04 10:11 meep New Issue
2018-01-04 10:11 meep File Added: 20180102_222308_Nuclear_Winter_v1_104.0.1-92-g4409317 maintenance.sdfz
2018-01-04 10:12 meep File Added: infolog.txt
2019-01-22 19:37 Kloot Changeset attached => spring develop 3a14eb31
2019-01-22 19:37 Kloot Note Added: 0019678
2019-01-22 19:37 Kloot Assigned To => Kloot
2019-01-22 19:37 Kloot Status new => resolved
2019-01-22 19:37 Kloot Resolution open => fixed
2019-01-22 19:39 Kloot Changeset attached => spring maintenance 0ecf0328
2019-01-22 19:39 Kloot Note Added: 0019679
+Issue History