Dwarf Fortress Bug Tracker - Dwarf Fortress
View Issue Details
0011170Dwarf FortressTechnical -- Generalpublic2019-10-27 12:252021-03-04 23:46
PCwindows 10x64
0011170: Crash after short time playing fortress mode "Midmap effective coordinate check out of bound"
I apologize if this is in the wrong category.
Whenever I load my fortress It will run for a short time and then crash to desktop without any error msg. When checking the error log there are a few messages from auto nestbox and then a spam of errors titled Midmap effective coordinate check out of bound.

I have enabled df to use more then 2gb of memory as I thought that may be the problem however that doesnt seem to be the case.
I recently built a new computer and am running a amd cpu if that is a known problem? my old pc had a intel cpu.

I use LNP if that helps at all. I googled for this and have seen it reported before but that was years ago and there didnt seem to be a fix anyway.
1. load save
2. wait 5 minutes
Thanks for your time
No tags attached.
related to 0001680resolved Toady One Crash with "Midmap effective coordinate check out of bounds" 
Issue History
2019-10-27 12:25cablekingNew Issue
2019-10-27 13:04LociNote Added: 0039561
2019-10-27 13:04LociAssigned To => Loci
2019-10-27 13:04LociStatusnew => needs feedback
2019-10-27 16:49cablekingNote Added: 0039563
2019-10-27 16:49cablekingStatusneeds feedback => assigned
2019-10-27 21:45risusinfNote Added: 0039564
2019-10-28 02:24PatrikLundellNote Added: 0039565
2019-10-28 09:10cablekingNote Added: 0039566
2019-10-28 10:43cablekingNote Added: 0039567
2019-10-30 14:13LociRelationship addedparent of 0001680
2019-10-30 14:13LociRelationship replacedrelated to 0001680
2019-10-30 14:14LociReproducibilityalways => random
2019-10-30 14:14LociSummaryCrash after short time playing fortress mode => Crash after short time playing fortress mode "Midmap effective coordinate check out of bound"
2021-03-04 23:46jecowaNote Added: 0040954
2021-03-04 23:50jecowaNote Edited: 0040954bug_revision_view_page.php?bugnote_id=0040954#r16664

2019-10-27 13:04   
Please upload a save demonstrating this crash to DFFD ( http://dffd.bay12games.com/ [^] ) and post a link here.
2019-10-27 16:49   
Hi. Here is a link. http://dffd.bay12games.com/file.php?id=14581 [^]
I am not 100% if i did it correctly. I apologize if I did not upload the proper/all the necessary files.

thank you for the reply.
2019-10-27 21:45   
Runs well for 15mins on vanilla linux intel x64. Maybe dfhack issue.
2019-10-28 02:24   
Migrants showed up after 10 minutes, at which time I killed DF.
Windows 10.1, Intel CPU, LNP r05 (not latest version, but latest DFHack) with DFHack enabled. Tried TwbT and STANDARD print modes.

Couldn't find any "Midmap" error messages.

Don't understand the 2 GB comment, as that's a 32 bit issue, and the LNP uses the 64 bit version of DF.
2019-10-28 09:10   
Hi. Thanks for taking the time to test my save.
Today i'm gonna take some time and try fiddling with a more settings to see if anything changes.
What i'm really curious about is what would be causing this error and if this error even is whats causing the crash. I couldn't really get a definite answer as too what causes this error when i was googling previously.
2019-10-28 10:43   
Hi guys. I've been running the game and haven't run into any issues again. I'm not really sure what was going on. I appreciate your help even though the problem appears to have simply gone away. Consider this case closed I guess. Still wonder what the error I received was pertaining too.
2021-03-04 23:46   
(edited on: 2021-03-04 23:50)
Just had this issue in 0.47.05. Was looking around on the embark map and sometimes the game would freeze up for like 5-10 minutes. Checked the error log and it was 300+ MB and consisted entirely of "Midmap effective coordinate check out of bounds" repeated on every line. I deleted the file and cleared up some more drive space. I recreated the world with the same parameters (including the seeds). The new world had the same file size as the old world, but the hashes were different. Neither save file had any problems with freezing up or the midmap error.

tl;dr - the issue might be caused by a full disk drive