Second Life and Virtual Worlds
You probably don’t know that Second Life group member lists do not fully load for groups with over 5,000 members, unless you manage a large group. And now the Lab will soon be having the servers NOT send the full list to the viewer. This change is a work-around for a problem impacting group chat.
This coming change is NOT related to the new 60-groups limit. That is having no measurable impact on group chat. But, downloading LARGE member lists is creating a problem, apparently whether 1 or 60.
Builder’s Brewery sent out an announcement about the Large Group Edit Change (SVC-4968 – readable by all) that rolled out this last Tuesday (week 46). The new code should be on all regions now. The Beta viewer has the code to take advantage of the change.
Whoever wrote the announcement wasn’t quite up on what the changes do and how they affect you but, for practical purposes they are close enough. If you have followed the coverage here, I think you’ve heard better details.
A quick recap of Large Groups, somewhere over 10,000 to 15,000 members, is they could not be loaded for editing. If you fiddled enough you might get a 20k or so group to load. The actual size of a list that could be loaded depended on how well SL was performing and your connection. This made it generally impossible to edit large lists. So, members that hadn’t logged into SL for a year or more could not be pruned out of the group. Roles in the group could not be changed. That has been fixed.
Oz Linden has given us some news on the crashing problem they have had with the Beta and Development viewer. The Lindens believe the current Beta viewer (3-4-1-265642) has the memory leak, or whatever, fixed. The crash rate is back to low rates.
For the techies, the problem had to do with how the cURL wrapper was threaded. The cURL thing has to do with computer network communication over networks. It is a programming library that makes it easier for programmers to implement communication protocols like HTTP and HTTPS. It helps with encrypting communications.
One more round of testing in the Beta viewer is in progress. Once completed the basic fix and changes will move to the main release viewer, likely next week (42).
It takes a couple of days of testing to collect enough data to make a determination on whether a fix is working or not. The current Beta Viewer was compiled on Saturday and released on Monday. If you have Auto-Update on, you got it before it was on the web site.
Wednesday we got three packages rolled to the Release Candidate (RC) channels. The changes for Large Group Editing were in the package that rolled to the Le Tigre channel. While the packages rolled to Blue Steel and Magnum worked well, something went wrong in the Le Tigre roll out.
Something in the code is miscalculating the prim cost/count and forcing the return of large numbers of prims. You can imagine the screams. Very quickly the Lindens realized they had a problem. While they didn’t know the cause as of Thursday, they do know a massive number of prims were being returned.
The Le Tigre regions were rolled back and the package running on Blue Steel, a maintenance package, was rolled over Le Tigre. Unfortunately that roll could not undo the damage of returned prims. So, the damaged regions had to be restored to the region state previous to the damaging roll out.
Not much news this week. Plus I have been trying to resuscitate dying laptops. Seems to be a rash of those this week.
UPDATE: 1:54 PM PT – Le Tigre had serious problems and is being rolled back to the previous version. The regions have to be rolled back to get an earlier version of the server software. That is an automated process. Next all the regions in Le Tigre have to be manually updated to a previous SIM state prior to the problems. There are a over 1,000 regions to do. It is going to take some time.
There was no roll of a new server package to the main channel. Last week no Release Candidates made it to the RC channels, so there was nothing to roll.
There is a the New Lag Problem. This problem is pretty much invisible to the Lindens, meaning it is not showing up in their stats. Nor is it an easily reproducible problem. Both of those things make it invisible to the Lindens for all practical purposes. However, those running events are pulling their hair out dealing with the problem.
So, if you are an event manager or promoter, you will want to record the date and time, nearest minute, the lag hit, get as close as you can. Attend the Server Beta and Server & Scripting user group meetings (Time & Location) and provide at least the server version, region name, and date time of the problem.
SVC-4968 – The large group editing problem JIRA is going to roll to the Release Candidate Wednesday 9/19. This is way ahead of what I was expecting. This means that sometime around noon anyone with a copy of the project viewer (see the JIRA to get a copy) can visit a region in the RC … Read more