Scripts "Freezing"

I was wondering if anyone else noticed scripts freezing recently since the time 1.5 came out. Through testing, I've noticed that it mainly happens when listening for something said, either with llSay() or llDialog()or llLinkMessage(), and the listening with either a listen() event or a link_message() event. Does anyone know how to fix this or what's causing it? If you need a demonstration, contact me in game.

Thanks.

I get this too, as I mentioned either in this thread (and it get rolled back yesterday) or in some other thread.

I've got 40 apartments split between two buldings in different sims. Each apartment has a multi-purpose, multi-script controler object. From time to time, maybe one out of the 40 ever 2-3 days, I get a freeze up on one. As they each email me once a day, a lack of that email is a sign it need to be fixed.

Just resetting the script doesn't do it. It stays frozen (unresponsive to vocal commands or touches) until I recompile it.

Seems to happen more in Miramare than Celadon, but I haven't had the Celadon apartments as long yet.

Yes, I see that too. Even the noddy Chopper Hoverboard freezes now (since 1.5, I'd agree), and I don't recall that ever happening before. However, in the case of this hoverboard it's not a terminal freeze, because it unfreezes on dismount.

And I think you're right that it's related to comms traffic in some way, unless this was purely coincidental.

Unfortunately, that's not much info to give the devs. If I find something more substantial, maybe a test case, I'll post it.

In the case of the Hoverboard, I would imagine that it is reset or at least at a quiescent state when the rider is not riding it, and it is in the owners inventory.

Some of the other items which remain resident in the sims may be suffering from memory leaks. If this is the case, what would be the approach to troubleshooting? Having asked that question, I admit that I do not know this to be a factor, and perhaps it is a "cop out" to suggest it... is it worth a "look see"?

You may be getting a stack overflow

If your not online, you will not be notified of it by message, and your script just stops.

Ive had it happen about 4 times now with my Texas Hold'Em table, and since it doestn add info as the game continues, that means a memory leak in LSL somewhere (ie, my variables change but do not grow as the game progresses).

Just my 0.02

I just don't like how LSL keeps changing, and certain commands go obsolete, or have problems. so what if I make a specialized script I am selling for a lot of money, and then a couple months down the road one of the commands are changed in the language cause of an unseen prior error?

This worries me and makes me wonder about doing any more scripting at the moment. Should I be warry?

One should always be wary, and ready to fix anything (within reason). Hopefully this does not happen often. I have to believe that one of the things that does get considered is the impact of the changes to the community at large. I believe that one such case is the issue of the llOnSit command that some people are using as a teleport command (at least I think that was the one... worry my WOM (write only memory) is taking over for a moment here).

There are so many people that would be negatively effected that I believe this command is not on the list to be removed, or even depricated. (one cen hope eh?)

Whatever it is, it is very annoying and Linden should do something about it. I made a Texas Hold'Em Table that has so many chances to freeze that it never makes it through an entire play, and if the lindens would like to see this, I would be happy to show them. This is a major problem in terms of payout for casino games. If my games don't payout, then there are many angree customers. Anyway, thanks for all the input guys.

-Doug

Douglas,

Whilst scripts do allegedly freeze, they dont freeze very often. If you're getting one particular game that freezes often you might want to work on the basis that there is a runtime error.

To follow up this hypothesis, you could check out this thread:

/54/7a/20290/1.html

Azelda