|
|
|
[
Permlink
| « Hide
]
Dzonatas Sol added a comment - 02/May/07 11:50 AM
Changed to bug as it appears to be a presence issue.
So do my login.
When SL crash (or freeze my computer, sometimes) i can't relog before several minutes, waiting server log me out to its side. Servers should be more reactive? Logging out process should be more important than logging in! server should engage immediate log out when user is logging in from same computer (or simply not to log out and continue as if user did not get off!) It is very annoying when experiencing SL when others avies are waiting to your answers, while in a training group, tp, sells, buys, alluring, ... I've found that if I keep trying I'm eventually able to get in ahead of the supposed five minute delay. I agree, it's annoying, and can be very frustrating when you're in the middle of something important like teaching a class or talking to customers. Perhaps a linden (or someone else who knows) can clarify why the five minute delay exists?
Long delays in crash reporting makes me kill the crash reporting process so I can log back on quickly.
I now have Edit, Preferences, General, Crash Reports set to Ask Before Sending. My request is that there be an option to send a crash report after logging back in, and being able to resume an interrupted activity. @Tex: Better to let SL Crash Reporter doing its job, so Linden Lab can analyse that log.
The logging out process begin AFTER Crash Reporter did send the log file to server. Longer the time is used by Crash Reporter, longer we must wait. What is awful is the way how logging out takes so much time after all! To get a 15% more reactive computer (loading files into RAM and+or video card, writing other files), do compress your NTFS volume. Good news, we know how troublesome this is, and has been for a matter of months. Fixed internally earlier by Zen Linden, watch for it soon. Syncing this issue with its internal counterpart...
Moved to SVC because this is a service problem, and not a "Crash" per se.
Verified on 1.18.1 Server
yessss! Reopened – noticed this again today and asked Zen. May require a backbone change.
Re-closing because further investigation shows that these problems appear to be a new and different issue.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||