SL Disconnect Problem

[VeraLou Elf]

Bonjour,
For a few weeks now, I can't completely close the viewer window, it remains open with the message "second life no longer responds" I ask to log out but it remains open without time limit, screen greyed out, unless I force the close CTRL + F4 or with the task manager.

After reconnecting, my recent items remained in my inventory like when you crash

[Nalates Urriah]

We need the info from your viewer's HELP->About... Paste it in this thread. That allows us to eliminate a large number of problems and hopefully get to the actual problem. Including the info saves you and us the time of stepping through all the common might-be this or that issues.

The lack of information may be why it has taken a week for you to get any answer.

When all else is failing and when you and those helping have no clue, look in the viewer’s log files. The viewer has various log files you can read to get an idea of what has gone wrong. Look at the log immediately after you crash or exit the viewer. Logs are replaced the next time a viewer starts. You’ll find the logs in:

Windows: C:\Users\[Win_login_ID]\AppData\Roaming\SecondLife\logs\

Mac: /Users/<username>/Library/Application Support/SecondLife/logs

You will change folder and file names (like: \SecondLife\) based on the viewer used... But, they are all similar.

• crashreport.log – This log is generated when the viewer crashes, the previous version of the file is overwritten. Rename this file if you plan to restart the viewer before examining the file. Otherwise, just read it with a text viewer (Notepad is good).

• debug_info.log – This file is internally formatted as an XML file. I never find it of much use. It is mostly the specs of your machine.

• SecondLife.log – This is the main log file. I find it the most useful. Start from the end of the file and work toward the beginning. Search for ‘WARNING’ and ‘ERROR’. With any luck, the messages there will give you an idea of the problem. Recent changes have added a section heading to parts of the file that can identify the general nature of the problem. There are lots of performance stats included.  At the end of a non-crash log, there are secession stats;  Run Time, Average Packet Size, Dropped Packets, Resent Packets, etc. The file is replaced and recreated for each viewer's secession.

• SecondLife.error_marker – I don’t know what information is inside. I don’t have a copy to examine as I write this.  The presence of the file indicates where, when, and what error happened. I think this is a disaster backup file for crash reporting in which information about the crash is retained in the event the crash handlers are destroyed before they can create the other more complete crash files.

• SecondLife.start_marker – There is no information inside. The presence of the file indicates how far into the start process the viewer has gotten. Whether the file exists or not is the pertinent information.

• SecondLifeCrashReport.log – This is another file internally formatted to XML.  It is created when the viewer crashes. I think this is the new version of the crash log. It is mostly text.

• stats.log – This is a short file containing network statistics. Similar information is in other log files. It is an easy-to-read set of stats that show how many packets were dropped and resent in a secession.

I find the SecondLife.log is the most useful file for tuning and troubleshooting the viewer. It is verbose and reasonably easy to understand. There is a Debug Setting that allows you to increase or decrease the level of reporting.

Most of these files are erased when the viewer starts. If you plan to send the files in with a trouble ticket or bug report, place copies in another folder before starting the viewer.

Marker files are temporary and may or may not exist at any given time.

Entries in the files associated with errors and warnings are labeled as such. That makes them easy to find by searching. Search and read through them starting at the end of the file and working backward.

Warning entries are common and do NOT necessarily mean there is a problem. Some warnings are a part of normal operation. Some errors are trivial and do not indicate a ‘noticeable’ problem in the viewer’s operation.

[VeraLou Elf]

Thank you Natales for your clarifications and advice.
And sorry for a late reply.
I'm not at all familiar with the files on my PC but I'd know now.
The above problem no longer occurs today, the closing of the viewer has returned to normal.
Have a nice day.