Crashes break attachment scripts.
closed
Lyra Bunny
I crashed last week and all my scripted attachments got broken and turned to off position. I had to reset them and turn them on to make them work. No mod ones are unable to do this, so I had to replace them.
Then after I fixed all that, not long after, this has now happened again on a disconnect during teleport.
I went years without issues, so in theory this is a new server side bug that has appeared somewhat recently.
I was on firestorm, but that shouldn't matter I don't think since the objects themselves are broken.
I hope this is fixed because its very stressful to have to redo all my outfits every time I crash if this is how it will be going forward.
Log In
Maestro Linden
closed
Lyra Bunny
Its a teleport crash so I think I'd need to crash/dc during the teleport to replicate it correctly? The first time it happened, I teleported from a No Script Zone and dc'ed during the teleport. The second time, I think it was a normal script area I was being teleported from.
I did notice my LSL bridge was way out of date too, so I've replaced it.
Its also possible its something to do with my router but wouldn't that just make the script reset to last state on disconnect?
But yeah think I would need to test teleport failure to replicate it. (Until now, the only thing that would happen in these cases is it would get reverted to the last script state).
I hope that helps! Hope you are having a great day!
Maestro Linden
Lyra Bunny: Okay, to test a teleport-based "crash" (going offline due to a failed TP), the easiest way to test is on the beta grid, which has some development regions which can't be visited normally. Trying to TP to one of these regions should cause your viewer to fail to TP and go offline 100% of the time.
To try that case, I did the following:
- Log in to the beta grid.
- Instructions here if it's your first time: https://lindenlab.freshdesk.com/support/solutions/articles/31000156725-accessing-aditi
- Visit a 'normal' location on aditi that allows scripts to run, such as secondlife://Aditi/secondlife/Dore/128/128/42 , and wear a scripted attachment
- I used this script, which announces the time every 2 seconds in chat:
default
{
state_entry()
{
llSetTimerEvent(2);
}
timer()
{
llSay(0, "The time is " + llGetTimestamp());
}
}
- Attempt to TP to a region that's running but is on an inaccessible network location. I used "Brad Empty" for this step.
- Observe that during shortly after the failed TP, your viewer is kicked offline
- Login again, and go back to a location like secondlife://Aditi/secondlife/Dore/128/128/42 , and see if your scripts are still running or if they have crashed
I tried this a few times, and my attached script continues to run in step (5).
Are you able to reproduce the bug when you try that?
Lyra Bunny
Maestro Linden I tried the steps on beta grid, and it seems to work fine, not getting the broken script issue. I'm really not sure how to replicate this bug, sorry for the trouble. It happened twice in a week (on normal grid) and now nothing. Which is a good thing, I suppose!
I still have the broken reborn body hud (and some other objects that broke) tucked away in an inventory folder since I didn't wanna break links in outfits folder. It definitely still doesn't work and it is no modify so impossible for me to have turned off/on manually.
Sorry for not being able to figure this disconnect bug out, thanks for the help.
Maestro Linden
Lyra Bunny: Thanks for trying. Please let us know if you do figure out a reliable repro case for this issue.
Maestro Linden
needs info
Maestro Linden
Hi Lyra Bunny can you please provide steps (and example scripts if necessary) that will produce this issue? Testing in Second Life Server 2025-03-14.13862207703, I'm not seeing any script failures when I try this:
- Rez a box and create a default script in it
- Attach the script to your avatar
- Touch the the box and see "Touched." from the script - indicating that it is running
- Click Develop -> Force an Error -> Force Bad Memory Access to crash the viewer
- Launch the viewer again, and login to last location
- Touch the scripted box again to see if it's still running
I see the "Touched" chat in (6) - as expected.