ID:1467156
 
BYOND Version:501
Operating System:Windows 7 Pro 64-bit
Web Browser:Chrome 32.0.1700.72
Applies to:Dream Seeker
Status: Open

Issue hasn't been assigned a status value.
Here's the hang info

The program dreamseeker.exe version 5.0.501.1217 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
 Process ID: 1fa8
 Start Time: 01cf0db2e980a556
 Termination Time: 129
 Application Path: C:\Program Files (x86)\BYOND\bin\dreamseeker.exe
 Report Id: 8d17680a-79a8-11e3-9f5f-20cf30e81171



The code was this:
mob/verb/change_fps()
var/val = input("what fps?") as null | num
if(!val) return
world.fps = val
Have you tested this in the newest beta? There've been a couple of threading fixes, so it's possible one of them is relevant. I can do some testing on this myself to see what's going on too.
In response to Lummox JR
Lummox JR wrote:
Have you tested this in the newest beta? There've been a couple of threading fixes, so it's possible one of them is relevant. I can do some testing on this myself to see what's going on too.

I can't get a 503 world to stay alive after someone joins it. It just freezes. No good info to offer you on that. Just noticed that this was happening in 501 towards the end of my session when I tried to change FPS seeker hung (seeker was hosting).
Just an update, the Daemon is also crashing in the same 503 hosting scenario.
Have you been able to replicate this with the newest beta, or latest stable version?