Zugg Software :: View topic - [2.03] Unconfirmed lockups that are not detected by the new anti-lockup code

Wizard Joined: 14 Aug 2004 Posts: 1269

This thread is for unconfirmed lockups in 2.03 that are not detected by the new anti-lockup code... This form of lockup results in the CMUD GUI not redrawing itself.

I think #ALARM can cause lockups that are not detected by new anti-lockup code. I have had two lockups so far where CMUD became unresponsive but was not using CPU. On the first occasion, I left it for a few minutes but it never did anything or redrew the screen. I had the Package Editor open. After the first one, I suspected a #ALARM because it was at about 5 pm, and possibly exactly 5 pm by my clock, and I have an alarm that fires on the hour (which just sends a blank line to the mud and echoes NO-IDLE to the screen).

So I created an alias called "createAlarm" with this value:

#ALARM +1 {
#WINDOW alarms {#echo fired at %time(c.z)}
createAlarm
}

I was able to reproduce the lockup when I next connected to the MUD (after about 10 lines of text) - not sure if I had the Package Editor open this time, but probably - but since then I have had no luck at reproducing it. Maybe someone else can have a go. I don't think this can be reproduced in a blank session, as it is almost certainly a threading issue, which won't show up with blank settings. One probably has to have fair amount of scripts to get this.

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

heh, I was posting something like this in another lockup thread that existed... after reading this one, I checked my own settings.

I have a ton of aliases and triggers and capture windows, but only two aliases that utilize any wait/waitfor/alarm-type thing. One alias has a loop that continually executes as long as I'm connected, with a #WAIT 600000, the other which has a series of #WAITFOR commands. I'll try disabling both and see if I still get freezes.

Wizard Joined: 14 Aug 2004 Posts: 1269

Yeah, I thought I'd start a new thread instead of my old one getting longer and longer and difficult for new beta testers to follow.