Well the problem is pretty self-explanatory... world.Export() "falls asleep" when pinging a Dream Daemon that is frozen/has crashed, in stead of timing out after 1 or 2 seconds as it normally should do.
Numbered Steps to Reproduce Problem:
I have made a demo to... demonstrate this bug:
1: run the "export" environment and host it at Trusted
2: click the "startup world" verb to startup the "crash" environment and trigger the proc with world.Export()
3: wait a few seconds to see if it exports successfully
4: connect to the hosted "crash" environment and click the "crash" verb
5: if you switch back to the "crash" environment, you will see that the messages stopped at "Pinging...". You can wait, a minute.. and hour... or even a day, and it will never display the "Failed!" message... untill you kill the Dream Daemon process that is being pinged.
Code Snippet (if applicable) to Reproduce Problem:
When the pinged Dream Daemon freezes for whatever reason, world.Export() should time out after 1 or 2 seconds and return 0.
world.Export() just falls asleep and never wakes up.
Does the problem occur:
Every time? Or how often? Every time.
In other games? For any frozen environment.
In other user accounts? Irrelevant.
On other computers? I only have one computer.
When does the problem NOT occur? It always occurs.
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.)
Not that I know of.
Calling world.Export() in a spawn() and sleep a second after the spawn()