As Immortal mentioned all doors can cause a hang forever, till kill -9
is used (under Linux). It is true for all Doors, DD and D3 commands cause
it. There has to be a way to check this, a deadman timer based on whatever
the current timeout is that will drop the hung task when not reset. This
is likely true of MPL programs as well, there has to be a way to break an endless loop (if MPL checking doesn't do it automatically). This would
also be true for Events, if they are using too much CPU time. There should
be OS ways of handling such things which is likely a software deadman timer tied to an interrupt that will force the task off when taking all the time.

The hang I had on Sep 08 took a number of hung tasks to kill. As I mentioned it showed nothing in the logs because there was no time to write the logs.
I tried a reset (using ssh to get in and reset it), but still tasks were hung and CPU was running at 100%. With a couple of ssh I got in and got enough
time to kill them all off and restart mystic. I knew it was hung when I couldn't login to the BBS. It took a couple of minutes to get the two secure shells going that I finally killed it with. What really cause the hang, I
can't be sure with no real data to pin it on it could likely be bugs in the
OS itself. I have had it happen on 32bit and 64bit Linux. I'm not sure of Windows10 as yet, I haven't run it long enough to have it happen I suspect as
I rarely run it any more than 24 hours a week (I do run mystic under it always). It is odd that Linux's own debugging didn't break the hangs as it
does others I've run in to from MythTV and the like or report the error.

--- Mystic BBS v1.12 A35 (Linux/64)
* Origin: Mystic AlphaTest bcw142.zapto.org:2323 (21:1/145.2)