0005518: 103.0.1-747 LogicDaemon desync

ID	Project	Category	View Status	Date Submitted	Last Update
0005518	Spring engine	General	public	2017-04-10 08:17	2017-05-10 01:00

Reporter	Google_Frog	Assigned To	Kloot
Priority	normal	Severity	major	Reproducibility	have not tried
Status	closed	Resolution	fixed
Product Version	103.0 +git
Fixed in Version	103.0 +git

Summary	0005518: 103.0.1-747 LogicDaemon desync
Description	This game desynced for LogicDaemon: http://zero-k.info/Battles/Detail/453892 Here are infologs reporting the desync: https://github.com/ZeroK-RTS/CrashReports/issues/700 https://github.com/ZeroK-RTS/CrashReports/issues/701 https://github.com/ZeroK-RTS/CrashReports/issues/702 https://github.com/ZeroK-RTS/CrashReports/issues/703 https://github.com/ZeroK-RTS/CrashReports/issues/704 https://github.com/ZeroK-RTS/CrashReports/issues/705 LogicDaemon seems to desync more often than other players so I will try to get their path caches.
Tags	No tags attached.
Attached Files	~~20170409_163925_DesertSiege_v2b_103.0.1-747-g2ef5870 develop.sdfz~~ (Attachment missing)

Checked infolog.txt for Errors

Date Modified	Username	Field	Change
2017-04-10 08:17	Google_Frog	New Issue
2017-04-10 08:17	Google_Frog	File Added: 20170409_163925_DesertSiege_v2b_103.0.1-747-g2ef5870 develop.sdfz
2017-05-10 01:00	Kloot	Assigned To	=> Kloot
2017-05-10 01:00	Kloot	Status	new => closed
2017-05-10 01:00	Kloot	Resolution	open => fixed
2017-05-10 01:00	Kloot	Fixed in Version	=> 103.0 +git
2017-05-10 01:00	Kloot	Note Added: 0017583

Kloot 2017-05-10 01:00 developer ~0017583	at least three separate cases of pointer invalidation could have caused this since 747, no longer makes sense to investigate.