Bay 12 Games Forum

Please login or register.

Login with username, password and session length
Advanced search  

Author Topic: How do I diagnose a crash?  (Read 642 times)

Fleshbits

  • Bay Watcher
    • View Profile
How do I diagnose a crash?
« on: November 01, 2019, 06:18:54 am »
I've been playing this fortress quite a bit and have gotten further than I ever have before. However, it has begun to crash at random intervals.

I figure it must not be due to settings, since I've gotten a good ten years of game play so far with the current settings.

How do I go about diagnosing the problem? I see there are several logs, but I don't see any error information in them. Where do I look? What can I try?

Are there any known ways to diagnose and possibly fix a save?
I'd really like to keep playing this fort!
Logged

Fleeting Frames

  • Bay Watcher
  • Spooky cart at distance
    • View Profile
Re: How do I diagnose a crash?
« Reply #1 on: November 01, 2019, 07:19:21 am »
Sounds like raid bug, see two threads below yours: http://www.bay12forums.com/smf/index.php?topic=174949.0
Logged

Fleshbits

  • Bay Watcher
    • View Profile
Re: How do I diagnose a crash?
« Reply #2 on: November 01, 2019, 07:50:39 am »
Logged

Fleeting Frames

  • Bay Watcher
  • Spooky cart at distance
    • View Profile
Re: How do I diagnose a crash?
« Reply #3 on: November 01, 2019, 08:36:04 am »
Well, then I'd say try vanilla and see if it will crash similarly.

Retire-unretire can also help against other bugs, but I don't know about any other crash bugs being affected by it.
Logged

PatrikLundell

  • Bay Watcher
    • View Profile
Re: How do I diagnose a crash?
« Reply #4 on: November 01, 2019, 09:52:19 am »
There are no good ways to diagnose crashes in general. The raid equipment corruption bug is sufficiently understood that it can usually be identified. Other crash causes are usually not sufficiently understood to have reliable methods of identifying them.
A crashing save on DFFD may allow someone to identify the cause, if it's consistent (and "random intervals" doesn't sound consistent).
The 32 bit version can run out of memory if the game memory footprint exceeds 2 GB.
If you're using TwbT you may try to disable it and see if it help. It has been a crasher in the past, although it currently mostly cause crashes right on embark but not afterwards.

Note that a bugged save ought to be supplemented with needed info about OS (and version), DF version (not only version number, but also 32/64 bits, legacy, etc.). Tools/utilities are important, and omitting to mention mods borders on the criminal.

If the cause of the crashes can be identified it varies if it can be fixed. Sometimes a bugged creature can be killed, but many crash bugs don't have any known fixes. Retire/reclaim is a big hammer that sometimes work, at the substantial cost of having to repair the damage caused (stockpile contents spread all over the place, booze lost, prisoners released [kill those before retiring!], and other issues).
Logged