Zugg Software :: View topic

Apprentice Joined: 01 Dec 2006 Posts: 178

How stable is the 3.12?
I'm still using 2.37, and getting random errors when I reset a large amount of variables, crashable errors, that make sense, for example it stating that concat isn't done right, but when I do it another time it is fine?
So I'm considering updating to 3.12 but I'm wondering how stable it is compared to 2.37?
anyone?

Apprentice Joined: 01 Dec 2006 Posts: 178

Example of 2.37 error.

ERROR: Operator expression not allowed here requires two arguments

ERROR: Operator CONCAT requires two arguments <---------- times 48
ERROR: Operator LIST requires two arguments
ERROR: Operator CONCAT requires two arguments
ERROR: Operator CONCAT requires two arguments
ERROR: Operator CONCAT requires two arguments
ERROR: Operator CONCAT requires two arguments
ERROR: Operator LIST requires two arguments
ERROR: Operator CONCAT requires two arguments
ERROR: Operator CONCAT requires two arguments
ERROR: Operator CONCAT requires two arguments
ERROR: Operator CONCAT requires two arguments
ERROR: Operator CONCAT requires two arguments
ERROR: Operator CONCAT requires two arguments
ERROR: Operator CONCAT requires two arguments
ERROR: Operator CONCAT requires two arguments
ERROR: Operator CONCAT requires two arguments
ERROR: Operator CONCAT requires two arguments
ERROR: Operator CONCAT requires two arguments
ERROR: Operator CONCAT requires two arguments
ERROR: Operator LIST requires two arguments
ERROR: Operator CONCAT requires two arguments
ERROR: Operator CONCAT requires two arguments
ERROR: Operator CONCAT requires two arguments
ERROR: Operator CONCAT requires two arguments
ERROR: Operator CONCAT requires two arguments
ERROR: Operator CONCAT requires two arguments

All above are working and functional and it seems entirely random when it does this failure. but when it does it, its floating point calculations stops working and gives error as well.

Apprentice Joined: 13 Aug 2007 Posts: 166

I'm using 3.12 and I have way too many crashes for me to be happy... The program seems to screw up the session by itself. I created a new session... didn't have problems at the begining... then some erros / crashes came... and problems that made me create a new session... started to show up in that new one also.

Apprentice Joined: 13 Aug 2007 Posts: 166

Here's a common crash for me nowdays:

Posted: Thu Nov 26, 2009 10:55 pm

Those having crashes really do need to report them as soon as possible. Complaining about crashes do nothing unless Zugg can fix it.

Personally, I have currently 630 triggers, a few complex scripts, and a map with over 29k rooms mapped. I don't have crashes. In fact, I can keep CMUD running 24/7 and have no problems with it.

But then again, that's just me. :P

Charneus

Apprentice Joined: 01 Dec 2006 Posts: 178

the more I could get feedback from the better

Apprentice Joined: 13 Aug 2007 Posts: 166

I've been sending crash reports to all my crashes almsot, I hope it'll help... I just think it's been too quiet regarding the instabilities I've reported :P

Apprentice Joined: 03 Feb 2007 Posts: 170

I'm in the same boat as charneus, I have a stupid number of triggers and aliases, etc. and have no real issues at all with 3.12. No clue if some of the issues people are having are OS related, but am using Windows 7 Ultimate x64.

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

Those who are having problems may want to spend some serious time recreating layouts, recreating packages, and recreating sessions. I had a hell of a time getting rid of the corruption plaguing me, and I never got past the basic idea of which package it was (even the XML was showing no problems).

Apprentice Joined: 13 Aug 2007 Posts: 166

Matt, I have created a new session from scratch, cpy/pst-ing the settings I wanted from my zmud-imported session. Yet, that new session has gotten screwed. What I don't feel, is to spend a whole day every month with creating a new session because the old one screwed up itself. I've put various of my larger scripts into separate modules, hoping it would solve the problem. Some day ago I created a new session, used my old modules, and copied the entier content of my main setting... and ended up with getting the same errors. And I have sent crash reports for almost all crashes I've had...

Another funny thing I get:

"ERROR: Syntax error in Alias: areachange : error in floating point value"

due to the code:

temp4=3.4
#ALARM {+@temp4} {#SHOW text}

and when I restart CMUD, it works properly...

Apprentice Joined: 01 Dec 2006 Posts: 178

I've checked my code again and again, exported it to xml and reimported it, nothing fixes it, not even removing all the layout and starting over.

Posted: Mon Nov 30, 2009 6:03 pm

DanteX: Your crash above is coming from one of your user-defined functions. You really need to start a separate post about this issue and then post the script XML for the function that is causing the crash. Run the Script Debugger window to determine which script/trigger is running when you get the errors.

All of the errors that you have shown in this thread are specific problems with your scripts, and without seeing the scripts that you are importing, we can't really help.

The crash dumps that you send just go into a database, and if the crashes are related to a specific user script, then they mostly get ignored since I can't do anything without the script that caused the error.

Remember that this is the BETA forum and the purpose of using the Beta version is to help debug it. So you need to go through you zMUD import step by step to try and track down the exact trigger/script that is causing the problem.

Apprentice Joined: 01 Dec 2006 Posts: 178

I understand that this is the beta forum, I was asking the above question because I was considering switching to the beta if it was more stable.

As for the errors that are script specific errors.
That's just it, 95% of the time, the errors don't occur, but then for some reason seemingly at random, they do.

I've checked checked and checked some more and simply can't find out why it would do that, especially since it doesn't do it all the time, but only at random odd times.

Posted: Fri Dec 04, 2009 5:26 am

And in that regard, the 3.12 version is no worse than the 2.37 version, or even zMUD for that matter. Script specific problems can make *any* version unstable.

In the case of CMUD 2.x or greater, the cause is usually the #WAIT commands and not handling the multiple thread access to global variables properly using #SECTION. That can cause very obscure problems that are timing dependent and random. I have just as many reports of stuff like that in 2.37 as I do in 3.12. In fact, the crash dump reports on a "per user" kind of scale are worse on 2.37 than 3.12 right now.

Just remember that if *you* can't find a way to reproduce the problems, then what chance do I have to find the problem and fix it? Because we only have a small number of beta users these days, it just takes more and more time between versions to gather enough crash data. Eventually I'm going to just need to release the public version, even knowing that with the increased number of users I'll probably be swamped with bug reports. That's one of the reasons I am waiting until after the holidays to release the public version. I don't want to release something with problems right before I go away for two weeks for the holiday. I need to wait until I will have the time to do quick fixes to handle the stuff that has slipped past the beta testing.

Perhaps in public use I'll be able to gather enough data from enough users to track down some of these more obscure issues. But like I said, these things have happened in all versions of CMUD and zMUD at one time or another, so 3.x doesn't seem any worse.