View Issue Details

IDProjectCategoryLast Update
0022088AI War 2Crash/ExceptionNov 8, 2019 1:13 pm
ReporterNRSirLimbo Assigned ToChris_McElligottPark  
Status resolvedResolutionfixed 
Product Version1.003 Sortable Objectives 
Fixed in Version1.007 The Player/AI Arms Race Intensifies 
Summary0022088: Danger: CurrentFrameNumber changed from 55548 to 55549 during executionContext
DescriptionAnother day, another popup.

Potentially related to issue 0021648?
TagsNo tags attached.

Activities

NRSirLimbo

Nov 4, 2019 7:47 pm

developer  

ArcenDebugLog.txt (1,040,465 bytes)
20191105014306_1.jpg (344,802 bytes)

whetstone

Nov 4, 2019 9:03 pm

reporter   ~0054348

I also get these constantly, several times per game in the Linux build.

Chris_McElligottPark

Nov 7, 2019 4:12 pm

administrator   ~0054434

Probably fixed by the race condition stuff going away? If you see it again in 1.006 or later, please do let us know!

NRSirLimbo

Nov 7, 2019 5:49 pm

developer   ~0054444

Sadly negative on this one.

It is, however, a savegame from 1.005 played on 1.006
ArcenDebugLog-2.txt (1,152,813 bytes)
20191107234828_1.jpg (445,436 bytes)

Chris_McElligottPark

Nov 8, 2019 12:19 pm

administrator   ~0054456

Hmm, this could be a nasty one. I'm not sure what to do on it right now, as I'm not sure why on earth it would have this problem. It's going to be quite the code dive, I imagine.

Chris_McElligottPark

Nov 8, 2019 1:13 pm

administrator   ~0054460

Thanks!

* The "Danger! CurrentFrameNumber changed" error message has been removed from the game and won't bother people anymore.
** This was exceedingly rare for most people, but common for a few specific people. The best theory on this is that these people had exceedingly fast CPU cores, because on inspection of this code it was actually able to detect an "improper" state change that was really just "unlikely but fine." All of the improper cases would have been a lot more common to see, and seen across many clients. In this case it seems to have been a race condition between "work's done" and "make sure the frame didn't change," which were happening on a nanosecond scale.
** The worst case with someone having this change in an actual problematic way would be a multiplayer desync of some varying severity, but given that we already have network desync repair planned as a core key feature this isn't exactly a big deal. Originally this was also code that was defensively checking to see about single-player cross-threading issues, but those are all long-since fixed (2+ years ago).
** Basically this was a case of some false positive popping up in interrupting you for no good reason if your processor was fast enough.

Issue History

Date Modified Username Field Change
Nov 4, 2019 7:47 pm NRSirLimbo New Issue
Nov 4, 2019 7:47 pm NRSirLimbo File Added: ArcenDebugLog.txt
Nov 4, 2019 7:47 pm NRSirLimbo File Added: 20191105014306_1.jpg
Nov 4, 2019 9:03 pm whetstone Note Added: 0054348
Nov 7, 2019 4:12 pm Chris_McElligottPark Assigned To => Chris_McElligottPark
Nov 7, 2019 4:12 pm Chris_McElligottPark Status new => resolved
Nov 7, 2019 4:12 pm Chris_McElligottPark Resolution open => fixed
Nov 7, 2019 4:12 pm Chris_McElligottPark Fixed in Version => 1.006 Freedom Of Fleet Line Combination
Nov 7, 2019 4:12 pm Chris_McElligottPark Note Added: 0054434
Nov 7, 2019 5:49 pm NRSirLimbo File Added: ArcenDebugLog-2.txt
Nov 7, 2019 5:49 pm NRSirLimbo File Added: 20191107234828_1.jpg
Nov 7, 2019 5:49 pm NRSirLimbo Note Added: 0054444
Nov 8, 2019 12:19 pm Chris_McElligottPark Status resolved => assigned
Nov 8, 2019 12:19 pm Chris_McElligottPark Note Added: 0054456
Nov 8, 2019 1:13 pm Chris_McElligottPark Status assigned => resolved
Nov 8, 2019 1:13 pm Chris_McElligottPark Fixed in Version 1.006 Freedom Of Fleet Line Combination => 1.007 The Player/AI Arms Race Intensifies
Nov 8, 2019 1:13 pm Chris_McElligottPark Note Added: 0054460