View Issue Details

Jump to NotesJump to History
IDProjectCategoryDate SubmittedLast Update
0016778Stars Beyond ReachBug - OtherMay 19, 2015 8:51 pmMay 20, 2015 8:13 am
Reportercrazyroosterman Assigned ToChris_McElligottPark  
Status closedResolutionno change required 
Product Version0.822 (Revised Mouse Controls) 
Summary0016778: found a weird thing in my files
Descriptionwas going through my files for the things I needed for my other report and I found this other weird thing in the files im putting it here for you guys to look at.
TagsNo tags attached.

Activities

crazyroosterman

May 19, 2015 8:51 pm

reporter  

DrawGameErrors.txt (658 bytes)    
5/19/2015 12:54:09 AM (0.821) Mem: 237,858,816 Mode: SinglePlayerOrMultiplayerHost Plat:WindowsPlayer
-----------------------------------NullReferenceException-----------------------------------
Object reference not set to an instance of an object

  at MapTile.RenderTile (.UnityRenderer R, Boolean HasOpenWindowOrMouseIsOverWindow, Boolean BlockHUD) [0x00000] in <filename unknown>:0 
  at Game.DrawMetaMap (Boolean hasOpenWindowOrMouseIsOverWindow, Boolean BlockHUD) [0x00000] in <filename unknown>:0 
  at Game.DrawGame () [0x00000] in <filename unknown>:0 
  at Game.UpdateDisplay (Boolean IsFullVisualUpdate) [0x00000] in <filename unknown>:0
DrawGameErrors.txt (658 bytes)   

Chris_McElligottPark

May 19, 2015 9:11 pm

administrator   ~0041010

All good, this is a healthy thing and not really a true error. From 0.814:

* Now when the draw-game code hits an error it doesn't treat it as a fatal error unless it hits such errors for ten consecutive frames (or unless the game's in developer mode, we need to see the frequency of these things). All such errors, even those ignored by this rule, are logged to "DrawGameErrors.txt" in your RuntimeData directory.
** Basically this is to avoid the game freaking out because the UI was trying to process some information that the end-turn thread just changed in some uncomfortable way. Since the end-turn thread is the only one actually writing to sim-state, and those writes will always succeed, the read-only failures in the UI aren't of great concern.
** On the other hand, if we make some error in the rendering code it will generally cause an ongoing string of errors, not just the one, and we do want those to show up as normal fatal errors.




This is basically saying that there was a cross-threading conflict in one frame, but this caught it and no harm of any sort was done. But we wanted to log it just to be on the safe side.

crazyroosterman

May 19, 2015 9:16 pm

reporter   ~0041011

okay then that's good generally speaking whenever I find a new error file in stars ill post up here just for prudence's sake if nothing else.

Chris_McElligottPark

May 20, 2015 8:13 am

administrator   ~0041012

I appreciate it!

Issue History

Date Modified Username Field Change
May 19, 2015 8:51 pm crazyroosterman New Issue
May 19, 2015 8:51 pm crazyroosterman File Added: DrawGameErrors.txt
May 19, 2015 9:11 pm Chris_McElligottPark Note Added: 0041010
May 19, 2015 9:11 pm Chris_McElligottPark Status new => closed
May 19, 2015 9:11 pm Chris_McElligottPark Assigned To => Chris_McElligottPark
May 19, 2015 9:11 pm Chris_McElligottPark Resolution open => no change required
May 19, 2015 9:16 pm crazyroosterman Note Added: 0041011
May 20, 2015 8:13 am Chris_McElligottPark Note Added: 0041012