View Issue Details

IDProjectCategoryLast Update
0005059Valley 1Crash/ExceptionNov 6, 2011 12:25 pm
ReporterTechSY730 Assigned ToChris_McElligottPark  
Status resolvedResolutionfixed 
Product Version0.534 
Fixed in Version0.539 
Summary0005059: Fatal Error in GC
DescriptionHey guess what, its that error again! Message and everything.

Same specs as the related issue.

Also, once again, no error traces of any kind.
TagsNo tags attached.
Internal WeightGame Crash

Relationships

related to 0003872 closedChris_McElligottPark AI War 1 / Classic Fatal Error in GC 
related to 0005124 resolvedChris_McElligottPark Valley 1 Fatal Error 

Activities

TechSY730

Oct 27, 2011 11:25 pm

reporter   ~0017265

And just for clarification, this happened when going from one room to another.

TechSY730

Oct 27, 2011 11:27 pm

reporter   ~0017266

Last edited: Oct 27, 2011 11:34 pm

Reloaded the world, seemed to reload just fine. No corruption like that other crash.

EDIT: Sorry, I mean like the other AVWW crash. Never had a corruption issue in any of my AI war crashes.

Chris_McElligottPark

Oct 28, 2011 8:02 am

administrator   ~0017273

Okay, thanks for the clarification. How long had you been playing for when this happened?

TechSY730

Oct 28, 2011 9:28 am

reporter   ~0017276

Hmm, about 30 minutes to an hour. Don't remember for sure.

Chris_McElligottPark

Oct 28, 2011 9:31 am

administrator   ~0017277

Thanks for the details!

TechSY730

Nov 1, 2011 10:44 pm

reporter   ~0017375

Nope, still got this crash in 0.536

Chris_McElligottPark

Nov 6, 2011 12:25 pm

administrator   ~0017448

Thanks!

* Previously it was still possible for the mono garbage collector to suicide itself during save operations if it had to resize a large buffer and the transient memory happened to be too low at the time.
** At core, this is a bug in the way that unity 3d handles lack of heap space, and it's something that we've had to work around with all our games during memory-intensive operations (rather than just garbage collecting automatically any choosing to get on its day -- which it could easily do -- the engine instead throws a fatal error and dies if you use more than 800MB of heap space).
** Preventative code has now been put in place to prevent these sorts of errors during buffer resizings, basically forcing a GC collection if there is more than 500MB of heap currently in use just to be on the safe side.

Issue History

Date Modified Username Field Change
Oct 27, 2011 11:24 pm TechSY730 New Issue
Oct 27, 2011 11:25 pm TechSY730 Relationship added related to 0003872
Oct 27, 2011 11:25 pm TechSY730 Note Added: 0017265
Oct 27, 2011 11:27 pm TechSY730 Note Added: 0017266
Oct 27, 2011 11:34 pm TechSY730 Note Edited: 0017266
Oct 27, 2011 11:34 pm TechSY730 Note Edited: 0017266
Oct 28, 2011 6:37 am tigersfan Internal Weight => Game Crash
Oct 28, 2011 6:37 am tigersfan Assigned To => Chris_McElligottPark
Oct 28, 2011 6:37 am tigersfan Status new => assigned
Oct 28, 2011 8:02 am Chris_McElligottPark Note Added: 0017273
Oct 28, 2011 9:28 am TechSY730 Note Added: 0017276
Oct 28, 2011 9:31 am Chris_McElligottPark Note Added: 0017277
Nov 1, 2011 10:44 pm TechSY730 Note Added: 0017375
Nov 6, 2011 12:25 pm Chris_McElligottPark Relationship added related to 0005124
Nov 6, 2011 12:25 pm Chris_McElligottPark Note Added: 0017448
Nov 6, 2011 12:25 pm Chris_McElligottPark Status assigned => resolved
Nov 6, 2011 12:25 pm Chris_McElligottPark Fixed in Version => 0.539
Nov 6, 2011 12:25 pm Chris_McElligottPark Resolution open => fixed
Apr 14, 2014 9:28 am Chris_McElligottPark Category Bug - Crash or Exception => Crash/Exception