Zugg Software :: View topic

Wizard Joined: 17 Jun 2006 Posts: 1201

Okay I have an AMD Athlon 64 3800+ processor and CMUD was working along just fine when suddenly it stuck my processor at 100% and locked up. I couldn't close it by clicking the red x or do anything. The screen quit scrolling, everything came to a halt. Once again I had to close it via task manager.

Anyone have any idea on what the problem is?

This is version 2.01 I am speaking of here.

Posted: Mon Aug 27, 2007 4:21 am

could have been an infinite loop... hard to tell with so few details about what you were doing when it happened

Posted: Mon Aug 27, 2007 4:29 am

Well there a few known problems with this BETA some of which are described here and here.

If you can more accurately recreate the problem and it's different from those posts then please describe.

Somethings to check is your use of #WAIT (if any) since there were several changes with the threading model in this version of CMUD.

Wizard Joined: 17 Jun 2006 Posts: 1201

Tech,

The problem is I don't know what caused it this time. I had someone attack me full out and it was just humming right along curing everything with ease and then that happen. There was no loop of commands sent or anything like that. It just stopped responding completely. I know it will probably be impossible to reproduce. Maybe it is related to the other thread. All my curing is using databases so at the time it was updating databases, running aliases, and processing triggers very fast.

The only infinite loops I have encountered are the very annoying #sayprompt and #echoprompt ones.

By the way, I never use #wait for anything. It doesn't exist in my system. I do, however, have many alarms being used.

Apprentice Joined: 13 Aug 2007 Posts: 166

Something that made my processor blast the roof was when I tried to correct a bug where I got 3 prompts in my main window, of which one was a copy, is it was actually 2, but looked like 3. Wierd I know. So when I tried to fix the error, and move them around, it made the program stop responding mostly, but I managed to send a bug report once.

D

Posted: Mon Aug 27, 2007 7:02 pm

Did you try pressing the ESC key? Sometimes this will abort an infinite loop in the background. But as you said, without more information, it's going to be hard to reproduce this one. It could be related to almost anything running in your scripts. For example, if you are using a command that isn't "thread safe" and I haven't got it marked in CMUD as not thread-safe, then using it could cause weird problems like this.