Second Life version 1.15.0 Issues
Saturday, April 28th, 2007 at 5:07 PM by: Michael LindenA big part of the 1.15.0 release was a revamp of the systems behind the Group (and Conference) IM mechanisms, moving from a single server to a distributed set of systems. Obviously, this migration didn’t go without a hitch.
This bug summarizes both the problem and the pain pretty well:
- VWR-513 Group IMs Not Working Properly
[ https://jira.secondlife.com/browse/VWR-513 ]
We have fixes for the following issues undergoing testing internally, and they should be deployed early next week. Unfortunately, to deploy them will require a short grid downtime (20-30 minutes). Once we have tested the fixes, we will announce a time for this update.
- “X has left the session” is not seen when someone has spoken then left the group IM session
- “X has left the session” message sent when it shouldn’t
- Group IMs take up to 5 minutes to get through to you after a teleport.
There is one more case that will unfortunately require both a server and viewer update. We will evaluate the timing of releasing this based on feedback - kicking everyone off the grid for 1-2 hours and requiring a new download is not something we take lightly, and while the problem is irritating, we don’t want to make the cure worse. The issue is:
- ”Group chat IM reopens and error is received when attempting to send a message after user has closed group chat session”
Please report additional issues seen in the 1.15.0 release at our Issue Tracker [ http://jira.secondlife.com ].
We anticipate making an optional viewer update available within the next week or two with many accumulated fixes.
Our apologies in advance for the inconvenience, and our thanks to the Residents while we continue to improve Second Life.


April 29th, 2007 at 1:19 AM
[...] The most glaring of the outstanding issues plaguing Second Life since the update are group IMs. The Second Life grid is to be taken down for a short time early next week to fix the worst of the problems with them, and one to two weeks later a new viewer with many bug-fixes. Details about that are here. [...]
April 29th, 2007 at 1:47 AM
[...] the memory leak that the previous version had, it’s not without it’s problems. The latest post on the Second Life blog acknowledge that, and warn us of more downtime, in order to fix the [...]
April 30th, 2007 at 1:42 PM
[...] when they don’t want to hear what we have to say on an issue. I would like to comment on a recent blog entry they made, so I am going to try tracking back to it here, just to see if it [...]
May 1st, 2007 at 5:11 AM
Is the illegible text going to be fixed?
Version 1.15 changed the way the chat text looks, changing it from hard to read in some conditions to virtually illegible much more often.
Is this going to change or is Second Life going to be left with absurdly bad chat text display forever?
…
May 1st, 2007 at 5:01 PM
[...] patch should fix several of the Group IM issues which have been present since the 1.15.0 update last week, including: 1) “X has left the [...]
May 1st, 2007 at 6:02 PM
[...] patch should fix several of the Group IM issues which have been present since the 1.15.0 update last week, including: 1) “X has left the [...]
May 1st, 2007 at 8:48 PM
[...] patch should fix several of the Group IM issues which have been present since the 1.15.0 update last week, including: 1) ‘X has left the [...]
May 2nd, 2007 at 9:19 AM
[...] be down on May 2 from 9am until 11 am PDT for 1.15.0 patches. The patch should fix several of the Group IM issues which have been present since the 1.15.0 update last week. This patch also fixes issues with [...]
May 2nd, 2007 at 9:49 AM
[...] patch should fix several of the Group IM issues which have been present since the 1.15.0 update last week, including: 1) “X has left the [...]
May 2nd, 2007 at 10:05 AM
[...] patch should fix several of the Group IM issues which have been present since the 1.15.0 update last week, including: 1) “X has left the [...]
May 2nd, 2007 at 10:49 AM
[...] patch should fix several of the Group IM issues which have been present since the 1.15.0 update last week, including: 1) “X has left the [...]