Frequent CTD Build: 10435095 v0.8.1a

I’m having frequent crashes to desktop in the last couple of days. I have a lot of crash files, but I’ll send my latest ones. I didn’t have this issue up until the newest update, so hopefully the data helps to get this sorted. I’ve already:

  • restarted computer
  • uninstalled/reinstalled
  • removed all previous saves, including from previous versions of the game
  • verified file integrity via steam
  • downgraded from medium map to small map
  • also affects populations under 100 (I had a new game running last save on a small map)
  • utd on all drivers
    Overall the crashing is the only thing I’ve noticed and this is the most I’ve ever had this game crash on me. It chugs a little when I get over 200 people but that’s an already known issue. I have this save, and older saves backed up in a different file. I also have the other crash reports if more are necessary.

DxDiag.txt (114.7 KB)
crash 05 02 23.zip (23.6 KB)

Adding that it also seems to screw up Steam?

I have to completely close out of Steam and re-open it in order to go to my library. After the crash, it will take my library and have it “scroll” downward so that I cannot select anything on my list. It also bugs out the steam overlay on some occasions. This is the only game where this happens to me, but still unsure if this is related.

Hi WallsOfGab,

Looking at your crash dump, it appears that the instantiation of a UI element (building upgrade icon) failed and then the subsequent use of that failed object caused the crash. We use Unity as our game engine and we compile into native C++ code using their IL2CPP technology. Typically that generated native code shouldn’t crash. In fact, you are crashing in code that is checking the validity of that failed instantiation.

The more relevant question is probably why the instantiation of that object failed rather than why the null check of it crashed the game. Looking at your DxDiag.txt, I see that you don’t have an abundance of available RAM.

I suppose it’s possible you are running out of RAM, depending on the size of your town. If you are running out of RAM, it might explain why your Steam client is also affected - Steam also tries to allocate RAM, can’t, and doesn’t handle it well. Just a guess.

It might be interesting to see some of your other crash dumps. If we see that you are crashing in random places, all when allocating objects, it would indicate that perhaps you are running out of RAM. If it is always crashing in the same place, that might indicate that there is something specifically wrong with that bit of Unity generated IL2CPP generated code. However, I could not repro the issue.

You might also run Windows Resource Monitor to monitor your available RAM as well as the RAM that is being used by Farthest Frontier. If you see that you are running out of RAM when crashes happen, that would be an explanation. If you see FF using more RAM than expected, that might point to a memory leak.

Also, if you are using any 3rd-party mods or cheats, I would like to know that as well. We have seen cases where mod use has caused crashes especially after an update of the Unity engine - which we did update for the first time in over a year, for the 0.8.1 release.

1 Like

Yeah - it’s an older computer, so it has older computer issues. But typically, I don’t generally have RAM issues for as long as I keep as many applications closed as possible - so I normally close out of everything before I play games. That could very well be happening to Steam then, because it just freaks out and can’t handle whatever’s happening after a crash.

I’ll send a zip of all the crash files I’ve had for Feb so far - there are a lot because I tried a bunch of different things. Thing is, is that it would happen even if my population was small. The oldest save I had before I removed it from my folder from when the game first started, I had just about nearly 300 people and it was running better than most bug reports that I saw at the time.

After a reinstall AND a restart AND deleting old games, I’ve managed a new save that hasn’t crashed on me yet, fingers crossed. It was getting unplayable at one point because as soon as I would make a new settlement, it crashed upon map-load LOL

And nope! No mods or 3rd party cheats, for this build or any previous builds. I typically wait until full release for reasons like this :laughing:

FF Crash Dumpadumps.zip (246.5 KB)

Aaaand one more, since I had time to sit and run the Resource Monitor. idk if this would be actually helpful but it is here:
Baseline, title screen, map load, 10 minutes, 30 minutes and by the time I was finished about 3-4hrs later.
My ram usage is hot garbo with 20-90MB free at a time
FF Resource Monitor 07 02 23.zip (1.7 MB)

Thanks for sending those it. They all look memory/RAM related. Though your Resource Monitor doesn’t totally indicate that you are running out of RAM, this one crash dump is pretty clear:

Makes me wonder if you are having issues with faulty RAM? Seems unlikely, but who knows.

Maybe try running Windows Memory Diagnostic and see if that tells you anything:

Sure thing!
So I ran it, my results decided not to pop up for me to take a screenshot, but it did give me a pop-up saying that no issues were found and that was it! I ran it twice, just in case - same result.
And I know I didn’t really /change/ anything to make it start working again, since I’ve been able to play the game for several hours again. It’s weird. :grimacing:

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.