Mantis Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0005161Dwarf FortressWorld Generation -- Generalpublic2012-02-15 22:192014-07-09 18:12
Assigned ToToady One 
PlatformAMDOSWindowsOS Version7
Product Version0.34.01 
Target VersionFixed in Version0.34.03 
Summary0005161: Game crashed during world generation
DescriptionDuring history generation of a medium world, the game crashed.
Steps To ReproduceGenerate a world using these settings:

Size: Medium
History: Long
Civs: Medium
Sites: High
Beasts: High
Savagery: Medium
Minerals: Sparse
Tags0.34.02, 34.01, crash, world generation
Attached Files

- Relationships
related to 0005053resolvedFootkerchief Crash at the end of worldgen 

-  Notes
lightman (reporter)
2012-02-17 21:41

Sorry, I don't think this is a dupe. I didn't get that error message and this was during worldgen not after.
lightman (reporter)
2012-02-17 21:42

isn't there some way to get Toady the crash dump? This was in the middle of world gen so it didn't save anything.
Knight Otu (manager)
2012-02-18 02:20

Can you give us the world gen info with seeds? It would be in gamelog.txt, its location depending on how many worlds you genned in the meantime. It should look something like this:

Generating world using parameter set CREATE WORLD NOW = 4335334
 Seed: kQYW02gMQoUKMAIe6qcO
 History Seed: EQAyOqgcSUwys3F7DEl8
 Name Seed: 6puoKglWr1Xq2rOr87pj
 Creature Seed: SiRvbW1nlajdDTDaxosn

The parameter set for your options should be CREATE WORLD NOW = 4434432, if I recall the options correctly.
lightman (reporter)
2012-02-19 21:35

This should be it. I found these values in gamelog.txt and matched them in the memory dump.

Generating world using parameter set CREATE WORLD NOW = 4434433
 Seed: ys37V8fJ7WJuAaX2ZP9T
 History Seed: Qk28ku1L7rBkMkKlG1KJ
 Name Seed: uzIAP77G2rJGRghqv9ra
 Creature Seed: CiB2JgLmheImTPIuybY9
aarongolliver (reporter)
2012-02-19 22:47

I'm also having this problem.
DF Version: 0.34.02, Phoebus_34_02v01 integrated pack, True Type fonts on
Platform: Intel Westmere Xeon
Memory total: 24 GB

removed aquifers
ram usage was about 1.7 GB before the crash
Crashes after generation reaches 550, as it's scrolling between regions, but before given the chance to accept.

World size: Medium
Histor: Long
Number Civs: Very High
Number Beasts: Very High
Savagery: Very High
Minerals: Frequent


Generating world using parameter set CREATE WORLD NOW = 4455444
 History Seed: GUQucaWcSWokGAoQMyOU
 Name Seed: gs0KcKUwsSMi4g2a0kS2
 Creature Seed: ycacsYmMus0GEoKQWmmA
Moogie (reporter)
2012-02-20 16:52
edited on: 2012-02-20 17:18

34.02 SDL (unmodded)

Windows 7 x64
Quad Core i5 (3.1GHz)
8GB RAM (1.9GB used by DF at time of crash)

I've done some extensive testing on this, and I think I've narrowed down the issue. Here are my results.

The crashes seem to occur reliably during "finalizing sites" when the 'Number of Civilisations' is higher than default, and both 'Population Cap' and 'Site Cap' are turned off.

I've been generating custom Large worlds to test this. My latest crashseeds are as follows:

 Seed: rZCzJBzuarkOtKKhGnaf
 History Seed: zdrDmK6nzqJKi4DE2yhv
 Name Seed: BqjSQzst7YYUL3YXu4q6
 Creature Seed: fPgVwtBsqsoQ6Nxu7vUv

 Seed: 1bWYT4W8q4rr7XtnnuJ4
 History Seed: Pqcv0GdYaNXmDAL4zjhu
 Name Seed: LRSzj8R1ZyhoIVbDTDlO
 Creature Seed: KXA6syO6cK89OpyeYjx6

Steps to reproduce:
1. Create new world with Advanced Parameters.
2. (c)opy the Large Region settings.
3. (e)dit the new setting and change the "Population Cap" and "Site Cap" settings to Ignored, then set "Number of Civilisations" to anything above 60.
4. Begin worldgen. Let it run for at least 150 years.
5. Force worldgen to finalize. It will crash during "finalizing sites".

Screenshot: [^]

Update: I used a mempatcher to enable LAA and my crashes have gone, so it seems likely that the 2GB memory limit is the root of the issue (at least in my case).

Deathworks (reporter)
2012-03-29 02:20
edited on: 2012-03-29 02:22


I have just experienced a crash during world generation in 0.34.06 on Windows XP Professional SP3, which seems to be the same type. The crash was accompanied by the error message of an abnormal/extraordinary termination of the program and occured during the finalizing sites phase of world generation. The "current" directory of the saves directory is not empty. The parameters are:


- Issue History
Date Modified Username Field Change
2012-02-15 22:19 lightman New Issue
2012-02-15 22:19 lightman Tag Attached: crash
2012-02-15 22:19 lightman Tag Attached: world generation
2012-02-15 22:19 lightman Tag Attached: 34.01
2012-02-15 22:21 lightman Issue Monitored: lightman
2012-02-16 07:05 Footkerchief Relationship added duplicate of 0005053
2012-02-16 07:05 Footkerchief Status new => resolved
2012-02-16 07:05 Footkerchief Resolution open => duplicate
2012-02-16 07:05 Footkerchief Assigned To => Footkerchief
2012-02-17 21:41 lightman Note Added: 0020012
2012-02-17 21:41 lightman Status resolved => needs feedback
2012-02-17 21:41 lightman Resolution duplicate => reopened
2012-02-17 21:42 lightman Note Added: 0020013
2012-02-17 21:42 lightman Status needs feedback => assigned
2012-02-18 02:20 Knight Otu Note Added: 0020017
2012-02-18 02:20 Knight Otu Tag Attached: AWAITING UPDATE
2012-02-18 10:15 Footkerchief Relationship replaced related to 0005053
2012-02-18 10:15 Footkerchief Assigned To Footkerchief =>
2012-02-18 10:15 Footkerchief Status assigned => new
2012-02-19 11:08 Logical2u Relationship added related to 0005303
2012-02-19 21:35 lightman Note Added: 0020229
2012-02-19 22:44 aarongolliver Tag Attached: 0.34.02
2012-02-19 22:47 aarongolliver Note Added: 0020230
2012-02-19 22:47 aarongolliver Issue Monitored: aarongolliver
2012-02-20 16:52 Moogie Note Added: 0020300
2012-02-20 17:18 Moogie Note Edited: 0020300 View Revisions
2012-02-22 09:04 Footkerchief Relationship deleted related to 0005303
2012-02-28 09:29 Footkerchief Issue Monitored: Toady One
2012-02-28 09:30 Footkerchief Tag Attached: Fixed in 0.34.03?
2012-02-28 09:30 Footkerchief Tag Detached: AWAITING UPDATE
2012-03-29 02:20 Deathworks Note Added: 0021851
2012-03-29 02:20 Deathworks Note Edited: 0021851 View Revisions
2012-03-29 02:22 Deathworks Note Edited: 0021851 View Revisions
2012-06-06 13:33 Footkerchief Relationship added related to 0005283
2012-06-06 13:34 Footkerchief Relationship deleted related to 0005053
2012-06-06 13:34 Footkerchief Relationship deleted related to 0005283
2014-01-21 19:50 Footkerchief Relationship added related to 0005053
2014-01-26 08:46 Footkerchief Status new => resolved
2014-01-26 08:46 Footkerchief Fixed in Version => 0.34.03
2014-01-26 08:46 Footkerchief Resolution reopened => fixed
2014-01-26 08:46 Footkerchief Assigned To => Toady One
2014-01-26 08:46 Footkerchief Tag Detached: Fixed in 0.34.03?
2014-07-09 18:12 lightman Issue End Monitor: lightman

Copyright © 2000 - 2010 MantisBT Group
Powered by Mantis Bugtracker