Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Mazonas]

embark location chosen
embark profile chosen/customised
"Strike the Earth!"
*crash*

I've reported this as a bug, but I don't want to discount the possibility that I've done something stupid.  I've uploaded the region I'm using below in case anyone wants to try it for themselves.  Have I done something stupid?  Has anyone else had the same issue?

http://www.4shared.com/file/sTFaWXdu/region1.html

[Kamamura]

Took your saved region, started a new fortress, customized, embarked, everything OK.

So it's not the version, nor the generated region - there is probably something fishy about your local df configuration, operating system, hardware, etc. Possibilities are endless - do a memtest, check if you have enough resources, check logs if you have them, etc.

[billybobfred]

Occasionally the game crashes on embark.

Dunno what causes it, re-embarking with the exact same setup tends to work fine.

[Mazonas]

Huh.  That is really odd.  I tried redownloading DF 31.22 and moving the saved region into it and starting it again and... again... it crashed.  I've tried several different locations on the same world and it happens every time.

Hmmm...

[EveryZig]

I have had it sometimes happen and sometimes not happen. It only seems to hapen if you are starting a new fort on a world that previously had one.

[Jeoshua]

Try installing 31.22 fresh in a separate directory and try not to install and mods/graphics/etc.  Nothing more advanced than a "Create New World" seed should be changed.

If it crashes then? You have yourself a report-worthy bug.

But it'll still be something about your machine causing it, even if it is something Toady should address.

[Malibu Stacey]

Been happening to me occasionally since the first 0.31.xx version I used. As billybobfred says re-embarking at the same place with the same stuff often works perfectly fine.

I could hazard a guess at what the underlying problem is.

[Kamamura]

Huh.  That is really odd.  I tried redownloading DF 31.22 and moving the saved region into it and starting it again and... again... it crashed.  I've tried several different locations on the same world and it happens every time.

Hmmm...

As I said, there may be some problems with your computer setup - borked OS, failing memory, overheating, power supply issues, bad libraries, I don't know. Try laptop or a different computer, you'll see it works, at least sometimes. There may be a memory leak in the new version that may cause problems with low-mem setups.

[Girlinhat]

Just a toss out here, but, try a new world?

[Kamamura]

Just a toss out here, but, try a new world?

The world is OKAY, I tried it. And if it crashes every time, it has a value of reproducing the problem that plagues his setup.

[BurnCruise]

Same basic issue here. Tried re-embarking on the same spot with the same set up multiple times, each one ending in a crash. Tried a different area of that world, also a crash. Finally made a new world and tried 3 different areas without a single one crashing.

I even reinstalled the game to a different directory and completely deleted the original install. Im glad to know that it might be my laptop thats causing the problem though.

[Girlinhat]

I've had bugged worlds before.  I couldn't embark anywhere on it, or on other worlds I could embark but couldn't adventure.  It happens, bugs happen!  Try a new world, and if the problem persists, then it's a real issue.

[Mazonas]

Thanks for all the advice, guys.  Somehow, running the game in compatability mode fixed the problem.  Have noted this on the bug report I submitted.

[ZCM]

I've had bugged worlds before.  I couldn't embark anywhere on it, or on other worlds I could embark but couldn't adventure.  It happens, bugs happen!  Try a new world, and if the problem persists, then it's a real issue.

This sort of intermittent bug has a strong possibility of being memory corruption due to a wild pointer, which is Bad(tm).

[Jake]

Also, how much RAM have you got? It was possible to get by -barely- with 512MB in 40d, but the requirements have roughly doubled since then. That's caused a few crashes for me.