• All submissions to this site are governed by Second Life Project Contribution Agreement. By submitting patches and other information using this site, you acknowledge that you have read, understood, and agreed to those terms.
MAINTENANCE ANNOUNCEMENT - JIRA will undergo maintenance starting 1:00am PDT through 3:00am on Saturday 2010.03.20. Please do not enter issues during this time as the system maybe restarted.
Issue Details (XML | Word | Printable)

Key: SVC-438
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Simon Linden
Reporter: Torley Linden
Votes: 4
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
2. Second Life Service - SVC

Teleport to non-Public Access region takes a long time to time out and fails

Created: 19/Jul/07 01:24 PM   Updated: 03/Dec/07 07:20 AM
Component/s: Simulation
Affects Version/s: 1.18.0
Fix Version/s: None

Time Tracking:
Not Specified

Issue Links:
Relates

Linden Lab Issue ID: SL-49351


 Description  « Hide
I found out about this from Guy Linden. This is a solid repro for a problem that's happened in other contexts.
  • Try to teleport to a region that has Public Access disabled which you aren't allowed in (e.g., New Orleans Island or Sirapmoc).
  • Observe: The teleport bar will crawl slowly and never complete:
    (1) If you click Cancel button, your avatar will be frozen and unable to move. (Although you can right-click to sit on stuff, it immobilizes basic motion.) This requires a restart to regain functionality.
    (2) If you wait, the teleport will eventually time out and you'll be able to move, but it takes a long time.
    = Expected: You shouldn't be able to teleport at all, and see: "Could not teleport. You are not allowed into the destination." like in previous versions.

This causes problems because you don't have a way to tell in advance whether a region is Public Access-disabled (the control is found in the World menu > Region/Estate > Estate tab).



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Torley Linden added a comment - 23/Jul/07 11:20 AM
Retitled issue to distinguish distinct but related problems – be sure to see the linked issues too.

Dirk Talamasca added a comment - 02/Aug/07 03:45 AM
Confirmed.. Somebody come give me a push!! HELLLLLLLLLLLP!!

Torley Linden added a comment - 06/Aug/07 09:46 AM

Simon Linden added a comment - 13/Aug/07 02:22 PM
It's fixed - FWIW, if you wait a bit (about 2 minutes) you'll often pop out of this limbo state. It's fixed, however, so it should be OK when it works it's way out to release.

Argent Stonecutter added a comment - 25/Sep/07 03:22 AM
I've never had this happen when teleporting to a region I didn't have access to (in fact i can usually relog at the region I'm teleporting to as a workaround!), but I've had this happen when I'm teleporting home (and, yes, I had access to THAT as well, and could relog there).

So is this actually fixed, or is only one special case that's not actually common fixed?


Simon Linden added a comment - 25/Sep/07 09:32 AM
There's been a bunch of work on this specific problem, plus failures when teleporting home, when the system wants to send you home because a teleport to another area fails, it can't find an adjacent region, you're the estate owner but teleports are disabled, and so forth. I'm pretty confident we (it wasn't just me) fixed more than we broke, so please open another jira if you see problems. As always, easy-to-reproduce steps helps us fix it a lot.

Argent Stonecutter added a comment - 25/Sep/07 10:43 AM
According to the blog it hasn't been rolled out yet on the servers, so I can't file a new report.

I was mostly wondering if the work has been more along the lines of 'don't commit to teleports that you're not allowed to do', or 'correctly handle teleports that stall out'.


Simon Linden added a comment - 25/Sep/07 10:54 AM
It was more a "correctly handle teleports that fail". They didn't really stall, but it wasn't doing the correct stuff when one failed and thus ended up in limbo until it timed out.

richard noonan added a comment - 25/Sep/07 02:50 PM
Geez I am soooo happy this is getting fixed. I have reported this I bet a dozen times. I thought for the longest time i was me. WOW it is so Great to see its not me and its actually be fixed.
GREAT Work

Hanna Stardust added a comment - 26/Sep/07 02:39 PM
Is this bug fixed?
I tried to teleport to a region where I had no access just some minutes ago, and canceled (long waiting), and was unable to sit / move / teleport after that.

Alexa Linden added a comment - 03/Dec/07 07:19 AM
marking as fixed.