0000537: Crash on closing map with target0

ID	Project	Category	View Status	Date Submitted	Last Update

0000537	DarkRadiant	General	public	22.01.2008 00:37	26.03.2008 20:50

Reporter	SneaksieDave	Assigned To	greebo
Priority	normal	Severity	crash	Reproducibility	always
Status	closed	Resolution	fixed
Product Version	0.9.4
Target Version	0.9.6	Fixed in Version	0.9.6

Summary	0000537: Crash on closing map with target0
Description	See attached map. It contains an entity with a "target0" keypair. This is apparently hanging/crashing DR upon trying to shut down or close that map. Once the keypair is changed to "target1", it works fine. Note this exists in at least 0.9.4 as well.
Tags	No tags attached.
Attached Files	candleprefab4.rar (1,161 bytes)

Date Modified	Username	Field	Change
22.01.2008 00:37	SneaksieDave	New Issue
22.01.2008 00:37	SneaksieDave	File Added: candleprefab4.rar
22.01.2008 00:37	SneaksieDave	Description Updated
24.01.2008 13:19	greebo	Status	new => confirmed
24.01.2008 13:19	greebo	Status	confirmed => assigned
24.01.2008 13:19	greebo	Assigned To	=> greebo
24.01.2008 13:22	greebo	Note Added: 0001018
06.02.2008 15:08	greebo	Status	assigned => resolved
06.02.2008 15:08	greebo	Resolution	open => fixed
06.02.2008 15:08	greebo	Projection	none => minor fix
06.02.2008 15:08	greebo	Build	=> 2993
06.02.2008 15:08	greebo	Fixed in Version	=> 0.9.6
06.02.2008 15:08	greebo	Target Version	=> 0.9.6
14.02.2008 13:14	greebo	Relationship added	child of 0000577
26.03.2008 20:50	SneaksieDave	Status	resolved => closed

greebo 24.01.2008 13:22 administrator ~0001018	I could reproduce that. The reason is that DR assigns indices for all target keys on an entity. Both "target" and "target0" get the same index 0 assigned by DarkRadiant, and upon removal it tries to double-remove the observer. Assigning a "target" and "target0" is probably valid, so DarkRadiant needs to handle that case a bit more general.