View Issue Details

IDProjectCategoryView StatusLast Update
0005707Spring engineGeneralpublic2017-08-31 00:56
ReporterGoogle_Frog Assigned To 
PrioritynormalSeveritymajorReproducibilityhave not tried
Status closedResolutionduplicate 
Product Version103.0 +git 
Summary0005707: 103.0.1-1261 ktdm desync frame 8011
DescriptionLogs:
 * https://github.com/ZeroK-RTS/CrashReports/issues/1802 Sigero
 * https://github.com/ZeroK-RTS/CrashReports/issues/1804 Botan
 * https://github.com/ZeroK-RTS/CrashReports/issues/1805 [DK]Krudor
 * https://github.com/ZeroK-RTS/CrashReports/issues/1806 katastrophe
 
Note that ktdm has another ticket: https://springrts.com/mantis/view.php?id=5688

Battle: https://zero-k.info/Battles/Detail/465694

I think everyone is using sdz since the new stable. What is the archive cache rebuild supposed to fix?
TagsNo tags attached.
Checked infolog.txt for Errors

Relationships

duplicate of 0005688 closed 103.0.1-1244 Desync ktdm in frame 565 

Activities

Kloot

2017-08-16 03:09

developer   ~0018215

Last edited: 2017-08-16 03:50

as pointed out in 0005685, the checksums are insufficient because 1) once cached they do not protect against subsequent archive corruption (f.e. through disk failure) and 2) they derive from simple CRC's. an archive-cache rebuild would partially address 1). [edit: one of my assumptions appears to be wrong, a fresh cache only stores zeros]

these desyncs are more likely the result of corrupt synced data going undetected than an engine bug, since they affect some players (ktdm, LogicDaemon) constantly but almost never others.

Google_Frog

2017-08-16 04:54

reporter   ~0018216

https://github.com/spring/spring/commit/90a55a2b89af17750c05f70b94f26a80c03337bc has not built.

Kloot

2017-08-31 00:51

developer   ~0018309

Last edited: 2017-08-31 00:56

this may have been a case of "could not load model" which was seen in at least two other desyncs (0005727, 0005685); builds after 3263fc4e will netlog it since the involved players often don't seem interested in sharing their logs.

Issue History

Date Modified Username Field Change
2017-08-16 02:48 Google_Frog New Issue
2017-08-16 03:09 Kloot Note Added: 0018215
2017-08-16 03:21 Kloot Note Edited: 0018215
2017-08-16 03:50 Kloot Note Edited: 0018215
2017-08-16 04:54 Google_Frog Note Added: 0018216
2017-08-31 00:51 Kloot Status new => closed
2017-08-31 00:51 Kloot Resolution open => duplicate
2017-08-31 00:51 Kloot Note Added: 0018309
2017-08-31 00:51 Kloot Relationship added duplicate of 0005688
2017-08-31 00:56 Kloot Note Edited: 0018309