2025-07-21 23:44 CEST

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0005048Spring engineGeneralpublic2016-12-16 15:12
ReporterFLOZi 
Assigned ToKloot 
PrioritynormalSeveritycrashReproducibilityrandom
StatusresolvedResolutionfixed 
Product Version100.0 
Target VersionFixed in Version103.0 +git 
Summary0005048: Crash in Spring 100.0 with MCL
DescriptionInfolog indicates AI issue but iirc that is sometimes indicative of a borked stacktrace?

Infolog: http://pastebin.com/XS2uqdFU

Replay: https://www.dropbox.com/s/7p8yvl7ou3u2mzk/20160127_230401_Stronghold_beta_100.sdf?dl=0

MCL can be obtained via rapid, version was r1649, alternatively pull the repo from github https://github.com/SpringMCLegacy/SpringMCLegacy commit 1a403bdf6a49f7b3e387d5c745a2e07351feb905
TagsNo tags attached.
Checked infolog.txt for Errors
Attached Files

-Relationships
duplicate of 0005404resolved Spring.MoveCtrl.SetGunshipMoveTypeData called on tank will crash Spring 
+Relationships

-Notes

~0015578

abma (administrator)

does it crash with current development version, too?

translated:

C:\Windows\syswow64\msvcrt.dll 0x74CD43F9 ??:0
D:\Spring\spring.exe 0x00573285 rts/Lua/LuaSyncedMoveCtrl.cpp:123
D:\Spring\spring.exe 0x008148C0 rts/lib/lua/src/ldo.cpp:321
D:\Spring\spring.exe 0x00816469 rts/lib/lua/src/lvm.cpp:112
D:\Spring\spring.exe 0x00817CA9 rts/lib/lua/src/lvm.cpp:613
D:\Spring\spring.exe 0x0081405E rts/lib/lua/src/ldo.cpp:121
D:\Spring\spring.exe 0x00814B80 rts/lib/lua/src/ldo.cpp:378

~0015579

Kloot (developer)

Last edited: 2016-01-29 02:06

View 2 revisions

supposedly it was fixed by 51b1e53f26c586ac29ec2f60ac0a74a5aae5cdd5, but that commit looks like a no-op

edit: demo also desyncs for me with MCL 1a403bdf6a49f7b3e387d5c745a2e07351feb905

~0016461

FLOZi (reporter)

Last edited: 2016-06-30 20:32

View 2 revisions

Hard to say if present in current dev engine as 0005264 makes the game basically unplayable

~0016462

hokomoko (developer)

did you try to put GF's solution?

~0016463

FLOZi (reporter)

I'll give it a bash over the weekend and get back to you

~0016973

Kloot (developer)

looking at this trace again, most likely the same issue as 0005404
+Notes

-Issue History
Date Modified Username Field Change
2016-01-28 19:51 FLOZi New Issue
2016-01-28 21:28 abma Note Added: 0015578
2016-01-28 21:29 abma Status new => feedback
2016-01-28 22:12 Kloot Note Added: 0015579
2016-01-29 02:06 Kloot Note Edited: 0015579 View Revisions
2016-06-30 20:32 FLOZi Note Added: 0016461
2016-06-30 20:32 FLOZi Status feedback => new
2016-06-30 20:32 FLOZi Note Edited: 0016461 View Revisions
2016-06-30 20:33 hokomoko Note Added: 0016462
2016-06-30 23:54 FLOZi Note Added: 0016463
2016-12-16 15:12 Kloot Assigned To => Kloot
2016-12-16 15:12 Kloot Status new => resolved
2016-12-16 15:12 Kloot Resolution open => fixed
2016-12-16 15:12 Kloot Fixed in Version => 103.0 +git
2016-12-16 15:12 Kloot Note Added: 0016973
2016-12-16 15:12 Kloot Relationship added duplicate of 0005404
+Issue History