[1.1.0] Game crashing randomly after an hour of play

Farthest Frontier Bug Reporting
1

My game keeps crashing to desktop with no error message displayed after an hour or more of playing.

If i share a crash log here will one of you experts take a look?

4

What steps have you taken so far? Have you verified game files and updated drivers? Are you running any mods? Does your system meet the minimum requirements?

5

Yes i’ve verified game files and updated drivers. Not running any mods. My system is 7700 cpu. 7800XT GPU and 32 gb ram so easily meets the system requirements. Below is what AI said about my crash log.

1. Exception Details

Exception Code: 0xC0000005 (Access Violation – Read) Faulting Module: UnityPlayer.dll Faulting Instruction Pointer: UnityPlayer+0x5038e1 Invalid Read Address: [redacted] Exception Type: INVALID_POINTER_READ

The instruction:

Code

test byte ptr [r13+0x94], 0x3

indicates the engine attempted to read a flag from an object whose base pointer (r13) was invalid or already freed.

2. High‑Level Interpretation

Unity attempted to access a destroyed or corrupted object. This is consistent with:

  • A stale pointer inside a Unity Job System worker thread
  • An entity (villager, building, AI target, path node) being destroyed while still referenced
  • A race condition between main thread and job threads
  • Save‑state or object‑lifecycle inconsistency

This is an engine‑level crash, not a GPU or OS fault.

3. Call Stack Summary

Relevant frames:

Code

UnityPlayer+0x5038e1  ← faulting read
UnityPlayer+0x3bfe9d
UnityPlayer+0x57717f
UnityPlayer+0x577a2b
UnityPlayer+0x577ab9
UnityPlayer+0x6b3c1c
kernel32!BaseThreadInitThunk
ntdll!RtlUserThreadStart

These offsets correspond to:

  • Component update loop
  • Unity Job System worker thread execution
  • PlayerLoop synchronization

This pattern strongly suggests a job operating on an object that was destroyed or invalidated mid‑execution.

4. Likely Game‑Side Causes

Based on the engine version and common patterns:

  • AI referencing a removed building or job
  • Pathfinding node invalidation
  • Entity despawn while still targeted
  • Corrupted or inconsistent save state
  • Unity 2022.3.x job system race condition

5. Environment

OS: Windows 10 (generalized) Process uptime: ~20 minutes Memory usage: Low (commit peak ~132 MB) Dump type: MiniDump (registers + partial memory)

6. Reproduction Notes (User‑Side)

  • Crash occurred during normal gameplay
  • Not during loading
  • No GPU‑related errors
  • Crash is deterministic across multiple attempts → suggests corrupted state or AI loop issue
1 Like
6

Did your game generate any crash dumps? If so, can you send the latest one/few in for analysis?

They would be here:

C:\Users<USERNAME>\AppData\Local\Temp\Crate Entertainment\Farthest Frontier\Crashes

7

Do you not trust the AI analysis of the crash log?
:rofl:

2 Likes