Transaction or script failures in 1.23.5 viewer?

I updated to the new mandatory 1.23.5 viewer earlier tonight, and I've just started having problems. I'm wondering whether anybody else has noticed the same ones?

I was in a store testing food items, deciding which to buy... when I tried one platter, it didn't work at all, didn't give the item it was supposed to give, the blue menu for choice of items didn't come up... nothing at all happened. I figured the script must need fixing or something.

But then, I tried to buy a copy of a table... it should have given me a folder when I right-clicked it and clicked the 'buy' button, but again, nothing happened. It didn't subtract the money, didn't do anything at all. I tried several times, each time, nothing.

I didn't have the same problem with other items in the store-- I bought a couple of things, got samples from a few others, they all worked fine.

Has anybody else noticed this problem? Is it something to do with the new viewer? I'd appreciate any help or advice... thanks!

Haven't seen this. I would venture a guess that the sim involved might have been lagged enough that not all script events were getting processed.

Scripts run on the server, with input from the viewer, so one might have suspected the recent server update, if others saw the problem. It's possible for the viewer to fail to deliver what the server wants to see for events, but I think that's unlikely in this case because, coincidentally, I've been extensively testing a script that relies on detailed touch input from the viewer and haven't seen any problems. (Well, none that weren't bugs in my script. )

There are no changes in the 1.23.5 viewer code that would have any impact on scripts. High likely that is an issue with the server code.

I think Occam's razor definitely applies here.

We're having script issues too. Last night, we couldn't get either of two picnic blankets to rez poseballs.

I had something odd happen in the new viewer too last night that I cannot figure out. I had on a very simple AO, just a few stands in it, from Vista. I was in a store and several sentences (same sentence several times) dropped into local chat. The sentence named my AO, including the maker of it and said something like:

Vista 2.0v Basic Girl AO - Touched

It said this several times, and then stopped. What could it have meant?

Some one is perving on you!

LOL How did someone 'Touch' my AO?

When you see "Touched." coming out of a HUD, it usually means that you'll find a "New Script" in there, from an accidental hit of the New Script button while the editor was open. If yours doesn't have anything like that inside, it could have been a coincidence, someone nearby had the same one.

So... is there anything that can be done about this, or is it one of those things that we just have to wait for LL to fix?

A script that rezzes a demo item in my shop is failing approximately 20% of the time. I've never had problems with this script before, and have used it for almost two years. There are four copies in the shop, and all four are behaving similarly. I've replaced and reset them, but to no avail.

In the scripting tips forum, its been disclosed that LL changed how memory management works on mono scripts in an attempt to get better control over how they affect server load. A side effect of this is that some scripts are now failing with a stack heap overflow where this was not an issue before.

This may be what is happening, especially with scripts that require a lot of memory.

The MLPV2 Group was posting warnings that the new changes in memory management wear causing MLPs with lots of poses or lost of menus to fail.

Right -- crashed script, most likely.

Unless *you* were crashed, this means SL was fouled up. If you subsequently bought stuff, or were even able to move, then clearly this wasn't the case -- and I suspect you'd have mentioned that minor detail!

As mentioned above, unlikely to be the new viewer. Probably just normal foul ups.

That would cause scripts to get a stack heap error. It hasn't been independently confirmed yet, but I can't imagine what else could account for what I saw. Soen's post sums it up pretty well. It would only happen for Mono-compiled stuff like MLPV2. Original MLP is usually LSL-compiled.