View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006288 | Spring engine | General | public | 2019-08-31 14:09 | 2019-08-31 22:03 |
| Reporter | raaar | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Product Version | 104.0 +git | ||||
| Summary | 0006288: 104.0.1-1378-g00fda18_maintenance | luai fails to load, out of memory error | ||||
| Description | Since changing from 104.0 to 104.0.1-.... maintenance, i've been getting these [f=-000001] [LuaMemPool::LogStats][handle=LuaIntro (unsynced)] index=1 {numAllocs[*],allocSums[*]}={0,0} {int,ext,rec}Allocs={0,19435,0} {chunk,block}Bytes={0,0} [f=-000001] Error: [LuaUI::RunCallInTraceback] error=4 (LUA_ERRMEM) callin=AddConsoleLine trace=[Internal Lua error: Call failure] not enough memory [f=-000001] Error: [LuaRules::RunCallInTraceback] error=4 (LUA_ERRMEM) callin=Update trace=[Internal Lua error: Call failure] not enough memory ... [f=-000001] Error: [ExitSpringProcess] errorMsg="not enough memory" msgCaption="Spring: caught content_error: " mainThread=1 sometimes the game doesn't exit with the oom error but luaui doesn't load and the lua memory usage stands over 700MB. Using /luaui reload will lower the usage to a normal ~50mb level and restore the UI This ALWAYS happens on the first play attempt after changing between maintenance engine versions, then it stops happening! | ||||
| Tags | No tags attached. | ||||
| Attached Files | |||||
| Checked infolog.txt for Errors | Yes | ||||
|
|
I knew I had forgotten something. This is not a "minor issue", it's a "critical" one. There were two issues actually, sometimes after changing engine version, it hangs on the first try (this one is apparently fixed on 1378), then on the second I get this lua oom error / luaui fail issue, but it loads normally on subsequent play attempts. I'm disabling some widgets to try and figure out which is causing the problem, but this smells like engine bug as it didn't happen before and only happens once after each switch. |
|
|
the problem is due to the "gui_message_separator.lua" widget only |
|
|
This smells like a widget bug exposed by changes in Spring's console output. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2019-08-31 14:09 | raaar | New Issue | |
| 2019-08-31 14:09 | raaar | File Added: infolog_luaui_alloc_error_104.0.1-1378_maintenance.txt | |
| 2019-08-31 14:14 | raaar | Note Added: 0020100 | |
| 2019-08-31 19:56 | raaar | Note Added: 0020102 | |
| 2019-08-31 21:46 | Kloot | Status | new => closed |
| 2019-08-31 21:46 | Kloot | Resolution | open => no change required |
| 2019-08-31 21:46 | Kloot | Note Added: 0020106 |
