Scripts randomly and permanently breaking

Have any of you had problems with a script randomly just breaking, i.e. it no longer runs the code at all, even if you reset the script, reattach, anything else. More importantly any ideas what might cause this to happen?

This infamous "Running" checkbox in the lower left of the editor? That one's got me a few times.

I've seen some scripts do this, even if you check the running checkbox, change the script and resave, anything you do wont' fix it. Even pasting in the Default Script wont' work. The script is dead forever.

A related bug will always uncheck the running checkbox after you close and reopen the script. To fix it, add a space somewhere in the script (or just change something), save the script (which recompiles it), then check the running checkbox. All fixed.

I have often found that recompiles of scripts fix weird breakage between point releases (e.g. 1.4.2 to 1.4.3). As Hank noted, sometimes you have to add a space/delete a space to actually force recompilation.

Actually I had someone IM me this morning where a script simply 'stopped working'

I went through the usual 'don't get mad at me - but check...' list of:

Is the script still in the prim?
Is it running?
Are you on 'no script' land.
Have you tried relogging.


All to no avail - it seemed for all purposes that this guy's script had inexplicably just 'stopped'.

So yeah, I think there is a 'script stopping bug' going around out there -- I just wish I knew what caused it.

Siggy.

I have had the same problem, out of 100's of skates being sold and used on a daily basis with no problems, 2 people have came to me and said there's have myseteriously stopped working =/

I have also seen this bug. It really makes debugging difficult because you have to figure out that you didn't add broken code, the script is just ignoring you!

I have also seen it get to the point where adding a space (forcing recompile) doesn't get it started again.

My workaround is to copy and paste the text into a new script on the same object. That works every time.

-- D

Same here

I had a piece of furniture with a sit script / custom animation just stop working.

Also last night I was playing with some levers (a simple touch triggered rotation script with some linked messages)

The lever stopped responding to touch. When copied the copy was broken too.

I copied the script, deleted the old script and plopped it back in the same prim and it worked fine.

There is some kind of database link between the prim and a script in a prim. I think that gets screwed up sometimes.

yup.

I've actually given up trying to code one of my more script intensive projects, because it behaves differently every time it compiles. If it does anything at all. If it even compiles. And it REALLY is a pain to keep copying and pasting and renaming and deleting to get a script to run again every time you change something.

And we seem to be back to the content refresh bug, too, dont we?

e.g., click 'New Script'.... save.... uh... where's my script? ....deselect object... reselect object... ah. there it is. Ironically, a month after reporting this bug I got a 'solved' email last week. And now it's back.

oh. and at least one in three times I open a script it's blank. Not 'loading...' and then never actually getting there, but completely blank from the get go. Close it, reopen, and it's (usually) there.

Most annoying.

Kris, I see the exact same problems you are seeing. And from the Lindens ignoring bug reports, what's the point in submitting them if they aren't fixed?

I know Cubey had this happen a couple times to him... He passed the script to me, and it worked fine. But it wouldnt work for him.

I am interested in this. It is not something I have personally experienced, or even directly seen happen. If there is anyone who has this happen frequently on a script, please send it my way - rename it so I will know what it is and drop it on my profile in world. If you have an object that has the script in a broken state on it, I'd like to see that too.

Kelly, talk to Cubey. He and I saw this just yesterday. He made a simple cube with a script. His wouldn't work. He gave me the script, I stuck it in a cube, and mine worked. I then gave *that* cube to him, and it wouldn't work, nor would it work if he copied and pasted my (slightly) altered version of the script into a completely new object.

It was almost as if the script vm was ignoring him.

I have found that shift dragging the object where the script resides can fix a lot of freaky behavior. Dont ask why... *shrugs*
Black magic.

That's a really gr8 tip, Eggy -- the easiest workaround anyone has come up with yet. Barring fixing it, of course.

-- D

I have experienced: the content refresh problem, blank scripts, scripts that wont finish compiling, and scripts that won't run state_entry after you compile (yes, it was running).

That last one is particularly frustrating. The first time I compile, everything works fine, then I compile again and it won't run state_entry. So I copy the text out of the script, paste it into a new one, and it works again.

There's no point sending the script to someone else to look at, because it works for everyone else but me. LSL hates me. And you know what? The feeling is becoming mutual.