ID:2835718
 
Resolved
Compiling while a turf or area was open for editing in the map editor's properties pane could cause a crash when selecting a tile after compilation.
BYOND Version:515.1595
Operating System:Windows 10 Home 64-bit
Web Browser:Firefox 106.0
Applies to:Dream Maker
Status: Resolved (515.1596)

This issue has been resolved.
Descriptive Problem Summary: In certain circumstances, Dream Maker can crash when changing certain variables from the code definition (such as density), when instances with variations of the changed variable already exist on the map*.

*Note that my attempts to pin-point this issue were really hit-and-miss, but following the steps below consistently produces the crash. Overall, the issue appears to be temperamental, and may not be related to the presence of map instances.

Numbered Steps to Reproduce Problem:
1) Download the following test project: http://files.byondhome.com/Higoten/Tests/ Crash%20with%20instances.zip
2) Open the code file (test.dm) and the map file (map.dmm), so both are open in tabs.
3) Navigate to map.dmm. Using the Move/Select Tool, click on one of the purple turfs.
4) Navigate to test.dm, change the density of the turf definition from 0 to 1.
5) Compile the project.
6) Navigate to map.dmm. Using the Move/Select Tool, click on one of the purple turfs.
7) Observe the Dream Maker has crashed.

Expected Results: Dream Maker shouldn’t crash. I do not know if any map instance should have its density updated due to the code definition change.

Actual Results: Dream Maker crashes.

Does the problem occur:
Every time? Or how often? Every time when following the steps above. Inconsistent results otherwise.

When does the problem NOT occur? Testing other circumstances appears hit or miss. Small deviations from the steps above can result in the issue not occurring.
Lummox JR resolved issue with message:
Compiling while a turf or area was open for editing in the map editor's properties pane could cause a crash when selecting a tile after compilation.