Zugg Software :: View topic - [2.03] CMUD screen stops displaying MUD output

Wizard Joined: 14 Aug 2004 Posts: 1269

Can't reproduce the freeze. Deleted the extra windows, but tells are still showing up twice in the capture window. Very odd.

Posted: Tue Oct 09, 2007 6:42 pm

The hang with the settings editor open is something different, and I think I already have this fixed in 2.06. It's possible that the hang that Thinjon experienced is also fixed, but I'm going to stay logged onto Aardwolf all day today and see what happens. I'll also keep the settings editor open to see if there are any remaining lockups with that.

But I *did* find several cases where modifying the database in a background thread was still causing the database to refresh it's controls, including the TreeView in the settings editor. And doing something to a user interface control from a background thread is a big no-no. So I added some code to prevent this from happening in background threads, and that seems to have improved the settings editor lockups.

For my session on Aardwolf, I have set up a prompt trigger to capture the hp. I also set up some #capture triggers. I also added the trigger that was suggested to keep the character online. I left it running during lunch and it's still running after an hour, but I'll let it keep going to see what happens. Maybe I'll even play it a bit to keep my test character from getting deleted.

Apprentice Joined: 12 Jul 2004 Posts: 190 Location: Canada

Your character won't be deleted. You stand the chance of being archived if you are inactive for oh, say... 3 months or more, but even at level 1 we won't delete your character.

I'm not easily-found on Aardwolf, being a wizi imm all the time, but if you drop me a note (board personal;note write Xantcha) I will help however I can.

Posted: Wed Oct 10, 2007 1:57 am

Cool...always good to know some of the wizis :)

I've actually been playing most of the afternoon. It's fun to actually play for a change. I've been filling my to-do list with a bunch of various things to fix in the future. Getting the mapper to work on Aardwolf is a bit tricky and the mapper doesn't seem to work as well as it is supposed to. Also, I reproduced the bug where you can't delete rooms on the map (seems to be related to being in a different zone), as well as a zone rename problem.

Also, speedwalking isn't working properly still. Even though it doesn't crash, the "safe mode" doesn't seem to make the triggers in time and misses the room names as they fly by. Might be a side effect of some of the new threading stuff somehow.

I've been trying to stay in the game and not pop back and forth between Delphi to fix these issues. I want to see if staying on a long time ever triggers the hang. But it's looking really good from here. I've been keeping the settings editor open all of the time and haven't run into any hangs or crashes yet.

Posted: Wed Oct 10, 2007 2:02 am

Woohoo! I finally got CMUD to hang! (btw, I had forgotten to click Submit, so the post above was actually written several hours ago)

Anyway, about 5 hours into my Aardwolf session, I finally got it to hang. It was executing a background trigger (one of my many #NOMAP triggers) and was waiting for the trigger to finish. Looks like there is a case where the trigger can finish so quickly that it finished *before* the call to WaitForMultipleObjects. And since the thread is already finished, the Wait just hangs forever. And unlike the Wait that is called from the command line, which looks for the ESC key, the Wait for background triggers like this cannot be aborted with ESC.

There are several things I need to fix with this. First, since the Trigger threads are being created in the main thread, I think I need to also allow ESC to work with aborting them. Otherwise a hang in this can hang all of CMUD (as in the case above). Then, I also need to find a way to protect the calling code so that the thread cannot finish and fire it's Windows event before I call the Wait routine.

Hopefully this is the same type of hang that you were getting. It certainly hangs all of CMUD and ESC doesn't work, and it doesn't use any CPU time. So it sounds familiar. I had the Settings Editor open as well, but according to the Delphi debugger, there wasn't any CriticalSection locks being used.

I'll try to get this fixed tomorrow. And then I'll fix a few other bugs and get ready for the 2.06 on Friday. But after using CMUD for over 5 hours, I'm getting pretty happy with the stability now.

Posted: Wed Oct 10, 2007 2:04 am

Oh, and the speedwalk "bug" that I mentioned in the previous thread turned out not to be a bug. It was looking for room names at the beginning of the line, and during speedwalking, the MUD prompt is displayed before the room name. Once I unchecked the "Match room name at start of line" option in the mapper config, then speedwalking started working great. So that seems to be fixed in v2.06 now.

Apprentice Joined: 12 Jul 2004 Posts: 190 Location: Canada

Yes, the automapper can be difficult in Aard. I suggest "brief 0" and turning off "automap" before doing any mapping. With the right settings, once mapped you can turn brief back to 1, and automap back on without issue

Posted: Thu Oct 11, 2007 3:43 am

Did another 6 hours on Aardwolf today after hopefully fixing the hang bug, and it hasn't hung yet. I'm going to leave it running overnight, but it's looking pretty good. I'll move on to some other bug fixes tomorrow and it's looking very good for a Friday release of 2.06.

Posted: Thu Oct 11, 2007 5:07 pm

Didn't hang overnight, but my network connection also flaked out in the middle of the night and got disconnected. I came in this morning and it was displaying the screen about the IP address lookup failure. So that means my cable modem broadband connection dropped and when CMUD tried to reconnect, it couldn't do the DNS lookup for the hostname. And I have no way to tell when it happened.

I'll keep it running today while I work on some other bugs. But it's certainly looking a lot better than previous versions.