0000400: "Export image/info" causes the game to quit

(0000861)
Jiri Petru (reporter)
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 (manager)
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 (reporter)
2010-04-06 08:33

I had graphics turned off when it happened.

(0001463)
Logical2u (manager)
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 (reporter)
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 (manager)
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 (reporter)
2010-04-07 11:37
edited on: 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 (manager)
2010-07-16 21:05

Anyone still getting this one?

(0012885)
Logical2u (manager)
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.

Issue History
Date Modified	Username	Field	Change
2010-04-04 07:53	DaPatman	New Issue
2010-04-04 08:02	Jiri Petru	Note Added: 0000861
2010-04-04 08:11	Logical2u	Note Added: 0000863
2010-04-04 08:16	Logical2u	Note Edited: 0000863	View Revisions
2010-04-04 08:16	Logical2u	Note Edited: 0000863	View Revisions
2010-04-04 17:28	Qloos	Tag Attached: worldgen
2010-04-05 12:05	Footkerchief	Relationship added	related to 0000006
2010-04-06 08:33	DaPatman	Note Added: 0001462
2010-04-06 08:43	Logical2u	Note Added: 0001463
2010-04-07 11:03	DaPatman	Note Added: 0001800
2010-04-07 11:14	Logical2u	Note Added: 0001804
2010-04-07 11:37	SirPenguin	Note Added: 0001809
2010-04-07 11:37	SirPenguin	Note Edited: 0001809	View Revisions
2010-04-24 11:11	Footkerchief	Relationship added	related to 0001491
2010-04-25 11:46	Footkerchief	Relationship deleted	related to 0001491
2010-07-16 20:06	TomiTapio	Tag Attached: AWAITING UPDATE
2010-07-16 20:06	TomiTapio	Tag Attached: CLOSE THIS
2010-07-16 20:11	TomiTapio	Tag Detached: AWAITING UPDATE
2010-07-16 20:12	TomiTapio	Tag Attached: memory
2010-07-16 20:12	TomiTapio	Tag Detached: CLOSE THIS
2010-07-16 21:04	Footkerchief_test_user	Tag Attached: blah
2010-07-16 21:05	Footkerchief_test_user	Tag Detached: blah
2010-07-16 21:05	Footkerchief	Note Added: 0010470
2010-07-16 21:06	Footkerchief	Tag Attached: AWAITING UPDATE
2010-09-22 06:00	Logical2u	Note Added: 0012885
2010-09-22 06:00	Logical2u	Status	new => resolved
2010-09-22 06:00	Logical2u	Resolution	open => unable to reproduce
2010-09-22 06:00	Logical2u	Assigned To	=> Logical2u
2010-09-22 06:00	Logical2u	Tag Detached: AWAITING UPDATE

Notes
(0000861) Jiri Petru (reporter) 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 (manager) 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 (reporter) 2010-04-06 08:33	I had graphics turned off when it happened.

(0001463) Logical2u (manager) 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 (reporter) 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 (manager) 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 (reporter) 2010-04-07 11:37 edited on: 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 (manager) 2010-07-16 21:05	Anyone still getting this one?

(0012885) Logical2u (manager) 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.