App crash at beginning of cycle 84


omark789
  • Branch: Live Branch Version: OSX Pending

In the beginning of cycle 84 the app crashes at some point. The bug is likely not related to user activity or in-game events, because the exact moment of the crash varies.

MacBook Pro (Retina, 13-inch, Late 2013)
OSX Sierra 10.12.6
2,4 Ghz Intel Core i5
4 GB 1600 Mhz DDR3
Intel Iris 1536 MB

The Optimistic Factory Cycle 83-84.zip


Steps to Reproduce
Nothing in particular, just let the game run.


User Feedback


2 hours ago, TehPlayer14 said:

From reading the log, verify game files

Also you only have 4 gb of ram that's under minimum required to run

Which line in the log indicates he needs to verify the game files? Are you referring to the shader errors? That's normal on OSX and linux and can be ignored.

Regarding the RAM comment:

image.png.310ff63ff17494a1fbd152e20e1f4b39.png

Also the last few lines in the log are:

INVALID TEMPERATURE FOR CELL ENERGY MODIFICATION:
ID(1009), kj(-0.165755), maxT(348.149994), cell(29778), mass(0.001243), deg. chg(-277.773346), temp(237.170975)
Assert failure 'BREAKPT:' at simlib/UpdateTemperature.cpp(51)

 

This shows a bug with the temperature system and not something to do with RAM.

  • Thanks 1

Share this comment


Link to comment
Share on other sites

Ok an update to the poster:

@omark789 You missed a DLL dump next time provide it, its located in the same folder as game executable (it happens when you don't even see the crash report sending screen)

The save crashes at almost the end of the cycle 

My log however doesn't contain:

Quote

INVALID TEMPERATURE FOR CELL ENERGY MODIFICATION: ID(1009), kj(-0.165755), maxT(348.149994), cell(29778), mass(0.001243), deg. chg(-277.773346), temp(237.170975)

Assert failure 'BREAKPT:' at simlib/UpdateTemperature.cpp(51)

Tested on Windows 7

SimDLL_CRASH_release_255502_20180218-20.04.44 The Optimistic Factory Cycle 83-84.dmp

output_log.txt

Share this comment


Link to comment
Share on other sites
3 minutes ago, TehPlayer14 said:

My log however doesn't contain:

Could be a timing thing, it is common for error messages just before a crash to sometimes not be printed if the program closed before it got to printing the messages. Anyways there is nothing more a player can do here so lets just leave it to the devs to debug.

 

6 minutes ago, TehPlayer14 said:

DLL dump

FYI they are called core dumps not DLL dump.

Share this comment


Link to comment
Share on other sites


Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now