Release build crashes always after 30-60 minutes no error given - UnityPlayer.dll?

AlleJong · November 30, 2024, 9:59am

Dear reader,

After 5 years of fulltime work on my game it has reached an final development state. The release builds of the game always crash. I am an artist and not an programmer engineer, so for me this is tricky to grasp around what is happening. If someone recognizes something in my story, thanks for every thought, insight or shared knowledge! If i investigate issues i am always fascinated by perspectives from many people. The most radical repair is deleting big parts of an project and see if the crash stops. In this case my game has grown into an large finished project after 5 years, so i cannot afford to just disconnect big parts. Which would take a year to rebuild by now. Every test trying to repair this issue takes up to two hours per step. It is very though.

Signs of sudden Freeze:

Stand IDLE will cause also the crash eventually, player location does not matter. (Is an open world witha around 40 streaming scenes landscapes that connect with an persistent scene with player)
Freeze occurs after 30 to 60 minutes, always.
Sound keeps playing after freeze.
Blue windows loading dot appears, if then click the screen becomes white and asks to close the application.

With the help of “chatgpt01preview” investigating an player crash log it suggested the following:

Based on the crash report you’ve provided, the application has crashed due to an access violation error in the UnityPlayer.dll module. Here’s a breakdown of the information and potential reasons for the crash:

Error Details:

Error Message: error “Attempt to access invalid address.”)*
Exception Type: Access Violation
This occurs when the program tries to read from or write to a memory location that it doesn’t have permission to access.
Faulting Module: UnityPlayer.dll
This is the core runtime library for Unity applications.

Possible Causes:

Null Reference Exception:

The application might be attempting to use an object reference that hasn’t been set to an instance of an object.
Common in scenarios where scripts try to access components or variables that are not initialized.

Memory Corruption:

Issues like buffer overruns or memory leaks can lead to access violations.
Could be caused by custom native plugins or mismanagement of resources.

Third-Party Plugins:

The crash report mentions AudioPluginOculusSpatializer.dll, which suggests that an audio plugin could be involved.
Incompatibility or bugs within plugins can cause instability.