2 strange lock ups on new version

So this is the first time I've spent any amount of time in the new version, and so far I've had 2 strange lock ups. The client doesn't crash, but I lose all ability to move, chat, or interact with anything. I can still spin my camera view around but that is about it. Eventually the map starts going red, and the last time I noticed it claimed I was flying when I obviously wasn't. I hit stop flying, but that didn't help.

That sounds more like what happens when you lose network connectivity to me, rather than a SL crash or lockup.

It is exacly what I see when my wireless network drops. So I'd check your internet connection, and also check your ISP's status pages to see if they are admitting to any routing outages recently.

The only success I've ever had in curing it is that sometimes teleporting to a different sim allows the client to reconenct to the new simulator server, and you can then TP back to where you started. Otherwise, close, relog, wait while it logs you out.

Oh, and it has been doing it since I started playing - very sporadically, but, since way back last year some time, so it isn't version related.

I haven't noticed anything unusual. Trillian hadn't lost connection to any service. I"ll keep an eye on it.

Trillian is a LOT more robust - or rather, the IM protocols are - they use TCP for a lot of their control channels, which is reliable, and only transmit packets when you are actively chatting, or on a very slow heartbeat. I've even had Trillian stay connected while I unplogged a wired connection, untangled it and re-plugged it O.o

Secondlife is mostly UDP based, which allows for a LOT of packet lossage with no reporting, and has a very active level of chatter with the server.

Even more fun than that was "back in the day" when phone modems had such a huge timeout span (why not at only 5200 baud) that if your POWER went out momentarily you could sometimes let the computer reboot, reload the software and still have your active connections because neither the phone line or network routing percieved 'enough' time passing without an ACK packet to gaurentee you were gone.