Whirly Fizzle commented at 2019-03-24T16:37:30Z

I can confirm there has been a recent surge of reports of TP disconnects.
Unfortunately we (FS support) have no idea of the cause yet.
I can also confirm that this is affecting Singularity viewer - I've seen a lot of complaints in their group chat too - note that this is from Singularity users using the new alpha builds that have a fix for their older TP disconnect issue, plus the server version causing that disconnect problem with older viewers has been rolled back.

It seems that certain people are affected by this problem & others (myself included) can't reproduce it.

Whirly Fizzle commented at 2019-03-24T16:43:38Z, updated at 2019-03-24T16:44:10Z

Hiya Toysoldier,

Which Firewall & antivirus software are you using?
Roughly what % of teleports end in a disconnect?

The next session that ends in a TP disconnect, quit the viewer after disconnect and then before relaunching the viewer, please can you zip up the Firestorm logs folder & attach it to this JIRA issue using More Actions -> Attach files.
This wiki page tells you how to find your Firestorm logs: https://wiki.phoenixviewer.com/file_a_jira
Can you also note here the date & time of the disconnect and the region names you were teleporting from and to - this will enable Linden Lab to check the server logs.

If you don't mind, can you then see if you can reproduce the TP disconnect on the Linden lab viewer from https://secondlife.com/support/downloads/ & if you reproduce it, again zip up the logs from the LL viewer & attach them to this JIRA issue & note the date/time of the disconnect & the region you were teleporting from & to.
How to find logs on the LL viewer: https://community.secondlife.com/knowledgebase/english/how-to-report-a-bug-r224/Section_.3#Section__3

Thanks :)

Whirly Fizzle commented at 2019-03-24T16:52:07Z

Also to note, complaints about this started on Tuesday 19th March so we initially suspect a change in the Main Channel server http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Server/19#19.03.07.525089
Could this be an EEP issue? EEP went to main channel on that date.

Toysoldier Thor commented at 2019-03-24T17:13:45Z

I haven't used the LL viewer in a couple years.  I also have not tried to replicate the EXACT SAME TP as the ones that initially failed.  When one of them happen (last night it happened twice, on Friday it happened 3 times), i get forced to QUIT and log back in to my HOME sim... where my TP destination works.

Next time it happens, i will capture the FS logs and then Log back in to the sim i crashed from and try the exact same TP again.  My suspicion is that the issue is not 100% repeatable based on performing the same TP twice.  I suspect its based on the source or destination sim being in some resource condition when the TP happens - what ever that condition is.  

Your note that it could have been triggered after the Mar 19th main grid upgrade would be possibly right as most in FB said they have noticed it more so over the past few days.

Toysoldier Thor commented at 2019-03-24T17:15:23Z

i have posted this Jira bug into my FB timeline asking if others could add their experience or added details as well.

DieInAFire commented at 2019-03-24T18:49:55Z

I was told to comment here but the issue I'm getting is that I'm teleporting from my home location to another sim (Typically one of high load) and I'll be fine for 5-10 minutes and then I'll randomly just be disconnected. I've gotten the same issue on 3 different viewers and no adjustments I've made seem to fix it at all. I'm not actually sure what the issue is but it's rather irritating. :( 

mygoditsfullofstars commented at 2019-03-25T08:55:07Z

I have noticed a big increase in failed teleports too over the last week. Way more than normal. Seems completely random. The progress bar just sits there moving every so slightly for about 30 seconds or so, then, 'ding' disconnected from the grid.

vivipezz commented at 2019-03-25T15:09:21Z, updated at 2019-03-25T15:13:10Z

I am experiencing similar disconnects on TP, but also just wandering about, usually after 2-3 sim crossing.

The troubles, shared with many friends, started after last week release (March 19).

It happens a lot while using vehicles. I am involved in SL sailing and organizing races. Since last week, crashes happens so often, the races no longer make sense to be run.

Case: I am sailing, all seems good, sims stats are near perfect, then with no warning, I see i am no longer in control: steering, gestures, chat, nothing I do is passed through to my avatar.. then I get the “You have been logged out of SecondLife / You have been disconnected from the region you were in / View IM & Chat or Quit?” Pop-up message. I log back in SL, managed to sit on my boat again, but then I am no longer skipper, but crew… my avatar ghost still sits on the boat as skipper!

What I suspect : there seems to be an issue between the region sim and the login servers...as if they lost communication.... so when you cross from one region to the next, the system no longer knows whether you are online or offline... then the boat gets messed up as it gets a false information and gets rid of the avatar, but not completely (cf. “ghost” situation above)… 

IF we say that the latest release with EEP is the root of our problems... if i get it right, EEP allows you to keep the same windlight settings across regions during a session, so it creates a DISCONNECT between the region settings and your viewer's settings. Could it be possible that it create a DISCONNECT with your session beyond just the windlight settings, so that you get logged off?

NB: I usually use Firestorm.

Toysoldier Thor commented at 2019-03-26T04:37:37Z, updated at 2019-03-26T04:41:23Z

I TP Crashed tonight within the span of 1 hour.  I cleared all my logs after my first crash.  Then i crashed again on a TP from one Music venue (Muddys) to another (BigDaddys).  I was in my Firestorm x64 latest version.  I Zipped all my FS Logs on the main log folder.

When i tried to Login to LAST LOCATION... FS/SL took me to a place I was last night!  Even though  that is not where i crashed and i was already TPed to 3 other locations tonight.

SabastianNixon commented at 2019-03-26T07:44:37Z

I also been having issues of  Teleporting places  and then get  disconnected.  or crash or when i do get to teleport some where everything is Gray and take  1 to 2 mins to rez in..

Whirly Fizzle commented at 2019-03-26T09:24:21Z, updated at 2019-03-26T09:27:37Z

@toysoldier Thor

Thanks for the logs.
I can't see anything unusual in that session that ended in a TP disconnect apart from:

• You seem to be teleporting using the MystiTool HUD.
  Do you still suffer from the TP disconnects if you TP "normally" & even if you detach the MystiTool HUD?
  (2019-03-26T04:32:10Z INFO # newview/llviewermessage.cpp(8281) process_script_teleport_request : Object named MystiTool HUD 2.0.2 is offering TP to region Muddys position { 27201.656250, 15746.937500, 25.139999 }
  )
  This is just to rule out scripted teleports & that specific attachment being a problem - the MystiTool is a pretty heavy attachment.

• The disconnected teleport was between 2 very busy locations, which increases the change of a teleport time out, especially on a slow connection.

Activity that session: March 25 2019 - log times are GMT

• 04:09 - Agent Toysoldier Thor, logged into region Lafew

• 04:10 - teleported into region SolarWinds Music

• 04:30 - teleported into region Muddys

• 04:32:13 - teleport into region BIG DADDYS WORLD initiated

• 04:33:02 - viewer disconnects while agent is still in Muddy's region - so it seems you were stuck in a teleport from Muddys to BIG DADDYS WORLD for ~49 secs & never made the connection to BIG DADDYS WORLD & got disconnected during the TP.

  2019-03-26T04:32:13Z INFO #Teleport#  newview/llagent.cpp(5630) LLTeleportRequestViaLocation::LLTeleportRequestViaLocation : LLTeleportRequestViaLocation created
  2019-03-26T04:32:13Z INFO #Telport#  newview/llagent.cpp(4604) LLAgent::startTeleportRequest : Agent handling start teleport request.
  2019-03-26T04:32:13Z INFO #Teleport#  newview/llagent.cpp(5646) LLTeleportRequestViaLocation::startTeleport : LLTeleportRequestViaLocation::startTeleport
  2019-03-26T04:32:13Z INFO #Teleport#  newview/llagent.cpp(4457) LLAgent::teleportCore : In teleport core!
  2019-03-26T04:32:13Z INFO #  llui/llfloater.cpp(756) LLFloater::closeFloater : Closing floater worldmap
  2019-03-26T04:32:13Z INFO ##  newview/llagent.cpp(4715) LLAgent::teleportRequest : TeleportLocationRequest: '1145691116475392':{ 65.000000, 130.000000, 25.000000 }
  2019-03-26T04:33:02Z WARNING #  llmessage/llcircuit.cpp(1075) LLCircuitData::checkCircuitTimeout : LLCircuitData::checkCircuitTimeout for 216.82.53.37:13001 last ping 100.161885s seconds ago.
  2019-03-26T04:33:02Z WARNING #  llmessage/llcircuit.cpp(1085) LLCircuitData::checkCircuitTimeout : LLCircuitData::checkCircuitTimeout for 216.82.53.37:13001 still dead, dropping.
  2019-03-26T04:33:02Z INFO #  llmessage/llcircuit.cpp(468) LLCircuit::removeCircuitData : LLCircuit::removeCircuitData for 216.82.53.37:13001
  2019-03-26T04:33:05Z WARNING #  newview/llworld.cpp(694) LLWorld::removeRegion : RegionDump: Muddys 216.82.56.29:13021 { 239616.000000, 317184.000000, 0.000000 }
  2019-03-26T04:33:05Z WARNING #  newview/llworld.cpp(700) LLWorld::removeRegion : Agent position global { 239657.062164, 317307.963928, 22.345898 } agent { 41.062164, 123.963928, 22.345898 }
  2019-03-26T04:33:05Z WARNING #  newview/llworld.cpp(704) LLWorld::removeRegion : Regions visited 3
  2019-03-26T04:33:05Z WARNING #  newview/llworld.cpp(706) LLWorld::removeRegion : gFrameTimeSeconds 1386.625244s
  2019-03-26T04:33:05Z WARNING #  newview/llworld.cpp(708) LLWorld::removeRegion : Disabling region Muddys that agent is in!
  2019-03-26T04:33:05Z WARNING #  newview/lltoastalertpanel.cpp(184) LLToastAlertPanel::LLToastAlertPanel : Alert: You have been logged out of Second Life.
  
  You have been disconnected from the region you were in.

Toysoldier Thor commented at 2019-03-26T17:35:28Z

That is correct. I TPed from Muddys to BigDaddys when this TP failure happened. And in this case I used my hud to get the LM ... But I have also TP failed from a TP from a friend... I have TP failed from a quiet sim to a venue.

You are only seeing one event. It is happening randomly.

I have TPed back and forth between two very busy Sims and I Never failed so it was not just because the Sims were busy.

Toysoldier Thor commented at 2019-03-26T17:36:40Z

I still see that LL has not looked at this bug ... Much less assignment it for investigation. I know from my FB community that lots of my friends are experiencing the same thing.

darkrainfox commented at 2019-03-26T18:16:12Z

I'm having this same issue the grey screen when trying to tp on my teleporter at my home 

Toysoldier Thor commented at 2019-03-27T00:59:12Z

Just had the first for tonight.  On my 3rd TP since i logged in.  And... the TP was sourced from a SEARCH result.  So its because my TP used was from the MistiTool hud.

navanaxsacratus commented at 2019-03-27T03:18:38Z

I've been experiencing this for several days, with today being by far the worst.

My teleports have been exclusively from landmarks in my Inventory. I can't seem to form a rhyme or reason why some of them result in fails. They are generally not from busy sims. When they do fail they tend to result in rollbacks in which I'm wearing previous clothing and such like.

DilliDallagio commented at 2019-03-27T04:46:50Z, updated at 2019-03-31T15:31:33Z

I have been experiencing these TP disconnects since last week's EEP roll in on the grid. Coincidence? Maybe. The viewers I have had these diconnects with are Singularity Test, Singularity Alpha, Firestorm, Kokua. The only viewer I have NOT had disconnects with is Cool VL Viewer.

My system is 64-bit linux so the choice of viewers I have is small.

Update 28/Mar/19:

After installing the needed 32-bit libraries and using the Second Life Linux Spur viewer, the number of TP disconnects is lessened by a large number but they still happen. Usually happens when either the originating point or the destination point of the teleport is a stressed region. The "About..." info:

Second Life 5.0.9.329906 (Second Life Release)
Release Notes

You are at 141.8, 161.0, 3597.6 in ARMENELOS located at sim10498.agni.lindenlab.com (216.82.51.204:13002)
SLURL: http://maps.secondlife.com/secondlife/ARMENELOS/142/161/3598
(global coordinates 202638.0, 343969.0, 3597.6)
Second Life Server 19.03.07.525089
Release Notes

CPU: AMD FX-8370 Eight-Core Processor (1400.5 MHz)
Memory: 15953 MB
OS Version: Linux 4.20.16-112.current #1 SMP PREEMPT Fri Mar 15 02:54:46 UTC 2019 x86_64
Graphics Card Vendor: X.Org
Graphics Card: AMD Radeon (TM) RX 480 Graphics (POLARIS10, DRM 3.27.0, 4.20.16-112.current, LLVM 7.0.0)

OpenGL Version: 4.5 (Compatibility Profile) Mesa 19.0.0

Window size: 1920x1029
Font Size Adjustment: 96pt
UI Scaling: 1
Draw distance: 64m
Bandwidth: 500kbit/s
LOD factor: 4
Render quality: 4 / 7
Advanced Lighting Model: Enabled
Texture memory: 512MB
VFS (cache) creation time: March 28 2019 09:47:02

J2C Decoder Version: KDU v7.2
Audio Driver Version: Undefined
LLCEFLib/CEF Version: Undefined
LibVLC Version: Undefined
Voice Server Version: Not Connected
Packets Lost: 9/2878 (0.3%)
March 28 2019 09:47:11

Update 31/Mar/19:

With regards to the comments about no disconnects due to not rendering the sky... Cool VL Viewer has never disconnected on me. The one major difference I can ascertain, as a user, between Cool VL Viewer and the rest is that Cool VL Viewer does not automatically change it's windlight rendering to whatever the region default is. Cool VL Viewer uses the Linden "default" settings for sky and water (to be honest, never even seen it progress through a day cycle but only because I am not usually in one region long enough to remember that it does). The user either has to use an external lua script to get the viewer to track windlight changes by region (a feature of Cool VL Viewer) or they have to make the change manually themselves. Otherwise, it is LL Defaults all of the time.

Perhaps there is some clue to be found. Why does Cool VL Viewer, that does not automatically track windlights, not disconnecting in this era of EEP when other viewers, who are affected by not having EEP code but trying to render EEP settings on regions, are?

Second Update 31/Mar/19

After reviewing the viewer log from Singularity (which disconnected me during a series of teleports I was attempting) and the log from Cool VL Viewer (doing that same run of teleports successfully), I found a couple of differences.

Singularity calls LLEnvironmentRequest a few times when a teleport is requested whereas Cool VL Viewer does not.

The last region I was teleported to successfully with Singularity started issuing errors 499/498 "Wired Chewed by Rabbit". Also when I requested a teleport to another region, that destination did not appear in the viewer log yet the viewer issued this "WARNING: removeRegion: Disabling region Crossbrook that agent is in!" error apparently while the teleport progress bar graph was being displayed (attempted a teleport from Crossbrook to Okemo Canyon). I was then disconnected. Cool VL Viewer has no reportings of errors 499/498, at least when I was doing the same sequence of teleports.

All of the teleports I did were manual, using the World Map. No scripts nor Landmarks were used.

Eva Paneer commented at 2019-03-27T07:19:06Z

It has happened to me so many times that I have given up tonight.  I am literally just standing talking to friends and I get the grey screen to quit.  Then if I try to TP home, I get stuck and then crash or hang in the air.  When I log back in,  I'm the infamous cloud.  I feel like I'm back in 2009 all over again.

I am not using FS  I am using Singularity  but those using FS and Singularity are both experiencing this. 

It's maddening and got worse this evening.

Cinderella Stromfield commented at 2019-03-27T10:34:16Z, updated at 2019-03-27T10:34:48Z

Yes,having this nasty bug as well . Coming crazy , when always have to relog. And my friend is having excatly the same issue !

SiennaReese commented at 2019-03-27T14:04:20Z

Having this issue on almost every single attempt to teleport. Once I am able to log back in, I seem to be wearing clothing or items that I was wearing the day before,  never what I was wearing when I crashed. I cannot seem to teleport using Search or landmarks in my profile or inventory, but have no issues if someone teleports me (using my RLV collar, teleports never fail). Please fix this issue, as it's quite annoying to get logged out and having to change my clothes every single time, and most times relog again after logging back in from the crash.

Toysoldier Thor commented at 2019-03-27T14:27:33Z

How long does it take or how many people have to confirm there is a consistent bug after the mar 19th update before LL will even look at this jira and issue ?

Time to escalate the visibility of this jira on social media in LL eyes?

Last night it happened on two of my alts and many times. And yes.. I have noticed one time when I said log in to previous location it took me to a place I was at the night before!

Toysoldier Thor commented at 2019-03-27T19:59:28Z

This is forwarded comments from another user in SL ...

Toy, if you are able to add comments, Last night I was working on a project that involves edited notecards inside an attached hud. I crashed 3 times in 6 hours all during TP attempts and 2 of the times my notecard which had been saved, used, edited and resaved repeatedly rolled back to a version that was over 2 hours old. My avi was reverted to previous clothes, skin and other attatchments that were consistent with the over 2 hour old notecard data so it seems to me that my entire experience was rolled back in entirety. The items I was working with and editing rezzed out on the sim were unaffected.

Whirly Fizzle commented at 2019-03-28T16:16:53Z, updated at 2019-03-28T16:17:04Z

This is the pattern that is being constantly reported - user attempts a teleport & gets disconnected.
User then relogs & attempts to teleport again & receives this error message: https://prnt.sc/n48c9w
User will receive the same "Teleport blocked" message several times after the relog before TP is allowed again.

Kyle Linden commented at 2019-03-28T23:28:50Z

Hi Toy (and everyone else commenting),

We're investigating this issue in earnest and appreciate your comments.

Thanks!

Whirly Fizzle commented at 2019-03-29T14:59:25Z

I just had a teleport disconnect. Yay my first one :D

• Agent: Whirly Fizzle (2e255955-e183-48c4-b9f9-1cd1b80db94e).

• Starting region: Testylvania Sandbox

• Destination region: Buncrana

• Date/time of disconnected TP: 29/03/2019, ~7.30 AM SLT.

• Log attached: Whirly_1.log

• Activity for this session:

  • 7.24 AM SLT: Logged into http://maps.secondlife.com/secondlife/Testylvania%20Sandbox/96/128/22
  • 7.28AM SLT: teleported to http://maps.secondlife.com/secondlife/Buncrana/221/31/25 (was checking BUG-226610).
  • 7.28AM SLT: teleported back to http://maps.secondlife.com/secondlife/Testylvania%20Sandbox/96/128/22 (after about 40 secs on Buncrana).
  • 7.29AM SLT: Attempted teleport back to http://maps.secondlife.com/secondlife/Buncrana/221/31/25
  • TP progress bar just stalled here: https://prnt.sc/n4olwi
  • 7.30AM SLT: Viewer disconnected before I connected to Buncrana
  • https://prnt.sc/n4om7j

Toysoldier Thor commented at 2019-03-29T15:10:28Z

Welcome to the group. :). I had two last night again. And two people in was with last night also had it... But often the residents in world believe it's just them and just new source of LAG. One person said..."weird I have a powerful laptop and havent had to crashes in forever..." . I told her... It's not just lag... It's a tp drop bug .

Kat Linden commented at 2019-03-29T15:12:25Z

Emma Krokus contacted support, also unable to teleport without being disconnected.

Liny Odell commented at 2019-03-31T10:57:46Z

Just got this info from a friend roaming around the grid.

Agent: tails41347 dd2d043d-34b2-4db4-99cc-36aec50b29ca
Starting region name:  Sailing Violet
Destination region name:  Heart of Dallas
Date/time of disconnected: 2019/03/31 03:45:40 SLT.
Type: TP

Whirly Fizzle commented at 2019-03-31T11:31:24Z, updated at 2019-03-31T12:53:55Z

Feedback from Torric Rodas, who can reliably reproduce the TP disconnects.
If he disables sky rendering (CTRL+ALT+SHIFT+6) he can teleport with no disconnects.

I didn't test this yet.
I'm not a good test candidate for this bug though, I've only had the TP disconnect happen once since this problem started.

Norton Burns commented at 2019-03-31T12:00:41Z

I currently have a Mac test build of Singularity, which because of an issue has been built with sky completely disabled by default. I can't make it TP crash, after many attempts.

I've also heard, anecdotally, that setting a permanent local sky helps [I have that set on Firestorm & as yet haven't been able to TP crash that either.]

That does broadly say 'EEP' to me, especially as the issue appears to coincide with the main server rollout of EEP.

hatake.kohime commented at 2019-03-31T21:31:45Z

After a few attempts, I finally got a disconnect. I first received the error: Problem encountered processing your teleport request. You may need to log back in before you can teleport. If you continue to receive this message, please check the Second Life Support Portal. I received this error a few times before it attempted to process the teleport. After processing, it disconnected me.

• Starting region: Firestorm Social Island
• Destination region: Kenophobe
• Date/Time: 3-31-2019 @ 2:26 PM PST

Whirly Fizzle commented at 2019-04-01T09:04:14Z

@hatake Kohime
That error message is the teleport throttle, which is pretty easy to hit if you do lots of rapid teleports.
It shouldn't be related to the eventual disconnect.

Toysoldier Thor commented at 2019-04-01T12:59:23Z

All yesterday for most of the time I was logged in I had de rendered the sky ... On a few of the many TPs the sky was normal. But I had Zero TP failures since. I posted this work around to others in FB and those that tried it so far have reported that the tp failures seem to go away if the sky is Derendered. It's not science proof but so far it seems that work around stops the TP disconnect failures.

Willow Wilder commented at 2019-04-01T16:35:16Z

Copy/Paste from Firestorm SUP-20425

Basically I'd be driving a train and then kabang!! the viewer makes a ding noise and then tells me I've been logged out of Second Life. As for providing a location indicator, that is an SLurl, heh that is the problem. It happens system wide. It could be all over the SLRR rails I've got access to, or know about. Or even exploring any of the city grids.

Character or agent name is Gokuji Yoshikawa
The location was: Owlet
And the time? (unknown)
Type: Railroad travel from the region where Owlet was and then back to the Tuliptree area.

Oddly enough their problems seem largely close to mine.

Toysoldier Thor commented at 2019-04-02T01:52:07Z

Bad News from me.... 1/2 hour ago... while Sky was not rendered - CTRL-ALT-SHT-6 ... i TP'ed to a friends place and i got hit with a TP disconnect failure. So... de-rendering the sky while TPing did not prevent the TP failure.

Whirly Fizzle commented at 2019-04-03T16:37:27Z

There is a potential fix for the teleport disconnects that was rolled to all 3 RC servers today - BlueSteel, Magnum & LeTigre.
Is anyone still able to reproduce the teleport disconnects when TPing between two RC regions?
If all goes well with this potential fix, I expect it will be rolled to the main channel regions next Tuesday.

NOTE!
If you are a Singularity viewer user, there is another bug affecting Singularity that is causing a disconnect ~ every 15 minutes &/or teleport disconnects.
This is a separate bug with a different cause to the one filed here.
Singularity have a proposed fix for this Singularity specific bug in their latest viewer build that can be downloaded here: https://virtual-nexus.xyz/down/
As far as I'm aware this Singularity fix will not fix the main TP disconnect bug that's affecting all viewers though.

Willow Wilder commented at 2019-04-06T09:24:51Z

Agent: (Minuet Voir) (955cb802-7b7e-4857-967c-ef449240039b).
Starting region name: Miamia
Destination region name: AITUI
Date/time of disconnected: 06/04/2019, ~2ish AM SLT. 
Type: (TP / region crossing) TP

log attached

Henri Beauchamp commented at 2019-04-08T18:20:41Z, updated at 2019-04-08T18:21:26Z

Whirly just pointed me to this JIRA.

Regarding my viewer (the Cool VL Viewer), it does also suffer from this TP issue. I did not get any for now today, but got 3 of them yesterday.

About the Windlight stuff, my viewer does not implement at all region Windlight but may emulate FS' parcel Windlight via a tiny Lua script, if the user choose so. Since the viewer nonetheless suffers from TP timeouts (exactly as described in the first paragraph of the description of this JIRA), Region Windlight/EEP is probably not the problem (or only indirectly).

I'd rather suspect a failure to connect at all to the arrival sim.

Whirly Fizzle commented at 2019-04-08T23:24:52Z, updated at 2019-04-08T23:25:28Z

LL blog post about the TP disconnects: https://community.secondlife.com/blogs/entry/2524-darn-teleport-disconnects/

Sunset Faulkes commented at 2019-04-09T14:58:11Z

Hi,

I got logged out TPing from

• Start region= Aich 60/194/2
• Destination region = Luitgard 46/70/7
• Viewer used - Firestorm
• Date/SLT time of disconnect - April 9th, 7:19 AM SLT
• Logs attached

Kadah Coba commented at 2019-04-10T09:33:07Z

Just noticed on my last TP fail that attachments revert and I see that's already be mentioned here at least once. Figured I'd explain a bit as to why that happens, at least to the best that I understand it.

Inventory assets (the thing actually in your inventory vs. the object in-world) only update on detach or log off (same difference). If you edit an attachment, and while it's still attached, make a copy of it in your inventory, the copy you made will be of the object when it was initially attached that session. This trick comes in handy if you need to undo every change since attach.

On crash or normal disconnect (eg. user internet died), a normal log off will eventually happen, either from a timeout or forced when attempting to login again before the timeout. In this case, attachments will get their normal logout detach event.

On TP failure or, I'd assume, region crash, the attachments do not get that detach, thus revert.

TL:DR, manually detach your attachment to force save it.

The fact there is a revert might shed some light as to where the TP fail is happening in the process. My 9000 mile idiots guess is somewhere when the pack getting handed to the receiving region.

Henri Beauchamp commented at 2019-04-10T11:39:47Z

@Kadah

No, the new failed TPs issue is not related with this behaviour, since it always existed in SL (well, at least, always since 2006, i.e. when I joined SL).

In the past, you could even get failures to save the attachment state by detaching and quickly reattaching the object to your avatar ("quickly" meaning a few seconds back in 2007, and under the second around 2010): this bug is now history (which means you cannot, alas, use it as a "feature" to recover the old state of no-copy attachments).

Kadah Coba commented at 2019-04-13T22:23:21Z

Had someone IM me on this issue, they are unable to comment due to the accepted status. They brought up something I didn't notice myself the couple times it has happened to me till they pointed it out. Seems like expected behavior for this type of failure, like being in a region that crashes.

If you log back in to "place last visited" it actually takes you to the place at the last normal logout, not the place at time of disconnect