2025-07-20 01:13 CEST

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0005661Spring engineGeneralpublic2017-08-31 01:11
ReporterGoogle_Frog 
Assigned To 
PrioritynormalSeveritycrashReproducibilityhave not tried
StatusclosedResolutionduplicate 
Product Version103.0 +git 
Target VersionFixed in Version 
Summary0005661: 103.0.1-1199 Crash on game end
Descriptionhttps://github.com/ZeroK-RTS/CrashReports/issues/1542
TagsNo tags attached.
Checked infolog.txt for Errors
Attached Files

-Relationships
has duplicate 0005677closed 103.0.1-1237 Long hang 
+Relationships

-Notes

~0018069

Google_Frog (reporter)

https://github.com/ZeroK-RTS/CrashReports/issues/1546

~0018075

abma (administrator)

watchdog triggered + no stacktrace:

https://github.com/ZeroK-RTS/CrashReports/issues/1542

~0018076

abma (administrator)

https://github.com/ZeroK-RTS/CrashReports/issues/1546

watchdog triggered, hang very likely is in lua code:

https://github.com/spring/spring/tree/103.0.1-1199-g0b3d408

rts/lib/lua/src/lvm.cpp:570
rts/lib/lua/src/ldo.cpp:378
/opt/mxe/tmp-gcc/gcc-4.8.1.build/i686-w64-mingw32/libgcc/./gthr-default.h:628
rts/lib/lua/src/lapi.cpp:813
rts/lib/lua/src/ldo.cpp:119
??:0
rts/lib/lua/src/ldo.cpp:465
rts/lib/lua/src/lapi.cpp:834
rts/lib/lua/src/lapi.cpp:245
rts/lib/lua/src/lauxlib.cpp:154
rts/lib/lua/src/lbaselib.cpp:378
rts/lib/lua/src/ldo.cpp:321
rts/lib/lua/src/lvm.cpp:613
??:0
rts/lib/lua/src/lapi.cpp:813
rts/lib/lua/src/ldo.cpp:119
??:0
??:0
rts/lib/mingw-std-threads/mingw.thread.h:157
/opt/mxe/usr/lib/gcc/i686-w64-mingw32/4.8.1/include/c++/functional:2073
/opt/mxe/usr/lib/gcc/i686-w64-mingw32/4.8.1/include/c++/functional:2029
??:0
??:0
??:0

~0018077

abma (administrator)

how does zk choose if the win64 or win32 version is used? can the user choose or does this happen automaticly?

~0018078

Google_Frog (reporter)

ZK doesn't use win64 yet because it seems easier to test for stability on win32 first and then move to win64. I'm currently waiting on a fix for https://springrts.com/mantis/view.php?id=5637 or a way to apply the workaround to those that would require it without impacting anyone else.

~0018079

abma (administrator)

then i would guess: there is still something wrong with the environment of win64 buildslave as basicly all crashes are win64 which requires manual installation. As win32 is default and there are no similar reports AFAIK... looks heavily related to win64.

~0018080

Google_Frog (reporter)

What do you mean? These all look like win32 crashes, they have the line "Binary Word Size: 32-bit emulated".

~0018097

Kloot (developer)

1542 and 1546 both hanged after very long AI games, f=100108 and f=177802 (99 minutes) respectively.

the latter also had "[f=0128745] Error: [LuaRules::RunCallInTraceback] error=4 (LUA_ERRMEM) callin=Save trace=[Internal Lua error: Call failure] not enough memory" occur during save, followed by a "[f=0128760] Fatal: [spring_lua_alloc_log_error][handle=LuaRules][OOM] synced=0 {alloced,maximum}={805322260,805306368}bytes".

~0018311

Kloot (developer)

like 0005722 / 0005700 / 0005699 / etc, AI's trampling over engine data
+Notes

-Issue History
Date Modified Username Field Change
2017-07-19 15:02 Google_Frog New Issue
2017-07-20 12:37 Google_Frog Note Added: 0018069
2017-07-20 13:44 abma Note Added: 0018075
2017-07-20 13:46 abma Note Added: 0018076
2017-07-20 13:47 abma Summary 103.0.1-1199 Crash on game end => (win64) 103.0.1-1199 Crash on game end
2017-07-20 13:48 abma Note Added: 0018077
2017-07-20 16:22 Google_Frog Note Added: 0018078
2017-07-20 17:35 abma Note Added: 0018079
2017-07-21 01:58 Google_Frog Note Added: 0018080
2017-07-22 01:24 Kloot Note Added: 0018097
2017-07-31 18:54 abma Summary (win64) 103.0.1-1199 Crash on game end => 103.0.1-1199 Crash on game end
2017-07-31 18:56 Kloot Relationship added has duplicate 0005677
2017-08-31 01:11 Kloot Status new => closed
2017-08-31 01:11 Kloot Resolution open => duplicate
2017-08-31 01:11 Kloot Note Added: 0018311
+Issue History