Dwarf Fortress Bug Tracker - Dwarf Fortress
View Issue Details
0000400Dwarf FortressWorld Generation -- Generalpublic2010-04-04 07:532010-09-22 06:00
DaPatman 
Logical2u 
normalcrashsometimes
resolvedunable to reproduce 
0.31.01 
 
0000400: "Export image/info" causes the game to quit
Once a world has been generated, pressing [p] to "Export image/info" sometimes brings up an error box. Clicking on OK causes the game to quit.
1. Generate a world.
2. Press [p].
It only appears to happen with larger sized worlds. It didn't happen when I generated a pocket world, for example.
memory, worldgen
related to 0000006closed Toady One GRAPHICS:ON causes runtime error 
Issue History
2010-04-04 07:53DaPatmanNew Issue
2010-04-04 08:02Jiri PetruNote Added: 0000861
2010-04-04 08:11Logical2uNote Added: 0000863
2010-04-04 08:16Logical2uNote Edited: 0000863bug_revision_view_page.php?bugnote_id=0000863#r265
2010-04-04 08:16Logical2uNote Edited: 0000863bug_revision_view_page.php?bugnote_id=0000863#r266
2010-04-04 17:28QloosTag Attached: worldgen
2010-04-05 12:05FootkerchiefRelationship addedrelated to 0000006
2010-04-06 08:33DaPatmanNote Added: 0001462
2010-04-06 08:43Logical2uNote Added: 0001463
2010-04-07 11:03DaPatmanNote Added: 0001800
2010-04-07 11:14Logical2uNote Added: 0001804
2010-04-07 11:37SirPenguinNote Added: 0001809
2010-04-07 11:37SirPenguinNote Edited: 0001809bug_revision_view_page.php?bugnote_id=0001809#r539
2010-04-24 11:11FootkerchiefRelationship addedrelated to 0001491
2010-04-25 11:46FootkerchiefRelationship deletedrelated to 0001491
2010-07-16 20:06TomiTapioTag Attached: AWAITING UPDATE
2010-07-16 20:06TomiTapioTag Attached: CLOSE THIS
2010-07-16 20:11TomiTapioTag Detached: AWAITING UPDATE
2010-07-16 20:12TomiTapioTag Attached: memory
2010-07-16 20:12TomiTapioTag Detached: CLOSE THIS
2010-07-16 21:04Footkerchief_test_userTag Attached: blah
2010-07-16 21:05Footkerchief_test_userTag Detached: blah
2010-07-16 21:05FootkerchiefNote Added: 0010470
2010-07-16 21:06FootkerchiefTag Attached: AWAITING UPDATE
2010-09-22 06:00Logical2uNote Added: 0012885
2010-09-22 06:00Logical2uStatusnew => resolved
2010-09-22 06:00Logical2uResolutionopen => unable to reproduce
2010-09-22 06:00Logical2uAssigned To => Logical2u
2010-09-22 06:00Logical2uTag Detached: AWAITING UPDATE

Notes
(0000861)
Jiri Petru   
2010-04-04 08:02   
The problem happened to me when I had custom graphics (or tileset?) enabled. Switching back to vanilla allowed me to export the map.
(0000863)
Logical2u   
2010-04-04 08:11   
(edited on: 2010-04-04 08:16)
Does the problem persist with graphics turned off, DaPatman?

If so, there may be another issue at work here.

Otherwise I'm going to claim this is a duplicate of all the other crash bugs with graphics.

EG: 0000006 or 0000217

(0001462)
DaPatman   
2010-04-06 08:33   
I had graphics turned off when it happened.
(0001463)
Logical2u   
2010-04-06 08:43   
How much RAM does your PC have?
If there's a world that it consistently crashes when you attempt to export the image, please upload the save to the Dwarf Fortress File Depot?
(0001800)
DaPatman   
2010-04-07 11:03   
I have 1 gig of RAM.

However, I now think it may just have been a one-off thing caused by the fact that my computer was increasing virtual memory at the time, since the problem hasn't repeated since that time.
(0001804)
Logical2u   
2010-04-07 11:14   
Yea, a lot of the crashes seem to be due to increased memory usage in this version and the way Windows seems to allocate memory.

I think it's something along the lines of, only 1/2 of the total physical memory can be allocated to an individual process? And just personally speaking, DF can pass 500 megabytes of memory usage. If you're also doing another intensive task at the same time - eg virtual memory, that'd increase the probability of a memory related crash.
(0001809)
SirPenguin   
2010-04-07 11:37   
Confirmed.

1 gig of RAM, 3 gig page file: no crash
1 gig of RAM, 16mb page file, forced low virtual memory via multiple IE launches: crashes during world gen


The error was a Visual Studios runtime error, claiming it was trying to terminate runtime in an unusual way. That may be important to add to the title.

edit: this was vanilla, and graphics = off

(0010470)
Footkerchief   
2010-07-16 21:05   
Anyone still getting this one?
(0012885)
Logical2u   
2010-09-22 06:00   
I'm finally going to close this one, since it seems like no one's reported anything like it since then, and it seems rather strongly linked to memory/virtual memory burdens.

People can PM me on the forums if this happens again to them, and I'll reopen this.