Descriptive Problem Summary:
Large changes to the .dmm file (such as adding extra 'Z' locations to the map, or chaning a specific icon map wide) result in Dream Seeker not being able to open the world. However Dreem Seeker is visible in the processes window in Task Manager, consuming large amounts of memory. Whilst in Dream Maker, there are no apparent errors, and if the map is moved to a directory out of where the environment file is stored, Dream Seeker opens as normal, and runs as normal, though without a map.

Numbered Steps to Reproduce Problem:
Continual running of the .dmb file, Dreem Seeker stacks in Task Manager.

Code Snippet (if applicable) to Reproduce Problem:
N/A, To my knowledge this is not a code problem.

Expected Results:
Dream Seeker should open and run normally, without any problems.

Actual Results:
Dream Seeker does not visibly open, however if checked in Task Manager, there is a Dream Seeker process open.

Does the problem occur:
Every time? Or how often? Every time the above steps are attempted.
In other games? N/A
In other user accounts? Yes, I've attempted with several other user accounts.
On other computers? Yes, attempted on four other computers, one of which is my other programmers.

When does the problem NOT occur?
Once the .dmm map file is removed from the directory that the BYOND environment file is stored in.

Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? (Visit http://www.byond.com/download/build to download old versions for testing.)
Problem has occured in various other versions, earliest being in the 4.2 regions.

Workarounds:
None as such, .dmm must be removed or deleted, and COMPLETELY repopulated with icons, which is incredibly time consuming.