View Issue Details

IDProjectCategoryLast Update
0005124Valley 1Crash/ExceptionNov 6, 2011 12:25 pm
ReporterDizzard Assigned ToChris_McElligottPark  
Status resolvedResolutionfixed 
Product Version0.538 
Fixed in Version0.539 
Summary0005124: Fatal Error
DescriptionI just got another Fatal Error message (in shallow ocean region), this one was worse than the first one because I wasn't able to exit the game afterwards through the menu. I had to use task manager to kill it.

Attached the error files.

TagsNo tags attached.
Internal WeightNew

Relationships

related to 0005059 resolvedChris_McElligottPark Fatal Error in GC 

Activities

keith.lamothe

Nov 6, 2011 8:19 am

administrator   ~0017442

Hmm, another out-of-memory. How long had you been playing, and how much memory did it say it was using in task manager (if you looked at that part of the screen while killing the process).

Dizzard

Nov 6, 2011 9:05 am

reporter   ~0017443

Last edited: Nov 6, 2011 9:05 am

Not sure the exact date, but I think the game had been released for about a week when I started playing. (I've been playing the same save the whole time)

I'm around lv 126 now.

I can't remember how much memory it was using, if it happens again I'll make sure to make note of it.

Chris_McElligottPark

Nov 6, 2011 12:25 pm

administrator   ~0017447

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.


And thanks in particular for the ErrorsReportedByEngine.txt -- that almost NEVER actually has any real information in there from an out of memory crash, but in this case it actually pointed me right to where the memory went over. Thanks for that!

Issue History

Date Modified Username Field Change
Nov 6, 2011 6:41 am Dizzard New Issue
Nov 6, 2011 6:41 am Dizzard File Added: ErrorsReportedByEngine.txt
Nov 6, 2011 6:42 am Dizzard File Added: UnhandledErrors.txt
Nov 6, 2011 6:43 am Dizzard Description Updated
Nov 6, 2011 8:19 am keith.lamothe Note Added: 0017442
Nov 6, 2011 9:05 am Dizzard Note Added: 0017443
Nov 6, 2011 9:05 am Dizzard Note Edited: 0017443
Nov 6, 2011 12:25 pm Chris_McElligottPark Internal Weight => New
Nov 6, 2011 12:25 pm Chris_McElligottPark Note Added: 0017447
Nov 6, 2011 12:25 pm Chris_McElligottPark Status new => 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
Nov 6, 2011 12:25 pm Chris_McElligottPark Assigned To => Chris_McElligottPark
Nov 6, 2011 12:25 pm Chris_McElligottPark Relationship added related to 0005059
Apr 14, 2014 9:28 am Chris_McElligottPark Category Bug - Crash or Exception => Crash/Exception