Issues with SLViewer

[RhiannaReach]

I previously posted the question about SL crashing within minutes of logging in. Well have tried it with another avi (an old non mesh)  and it worked OK with her. So now the question is why, with her and not Rhianna? TIA

[Nalates Urriah]

This section of the forum is generally about PEOPLE stuff. Tech questions go in the Technology Forum section.

When you have a tech question we need to know a lot to give an ANSWER rather than a guess. Use the viewer's HELP->About... and paste that info with your question.

The first troubleshooting step you have taken, try another avatar. Now try another viewer. Most Firestorm users keep a copy of the SL Viewer installed for testing purposes. AND... if you do have to go to the Lab for help, they will insist you use the SL Viwer to get their help.

Also, strip your avatar to the basic nude Classic avatar.

These steps will reveal or eliminate most of the possible problems on your side. Also, they provide info needed by the Lab to help.

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 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 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.

[Rowan Amore]

Well, she did wait 4 hours after posting in the Tech section to post here.  There, 36 views, here, 63.

Anyway...

5 hours ago, RhiannaReach said:

I previously posted the question about SL crashing within minutes of logging in. Well have tried it with another avi (an old non mesh)  and it worked OK with her. So now the question is why, with her and not Rhianna? TIA

Did you try logging the one in at a less busy area?  I generally use Tromp when I'm having issues.

[Prokofy Neva]

9 hours ago, Nalates Urriah said:

This section of the forum is generally about PEOPLE stuff. Tech questions go in the Technology Forum section.

When you have a tech question we need to know a lot to give an ANSWER rather than a guess. Use the viewer's HELP->About... and paste that info with your question.

The first troubleshooting step you have taken, try another avatar. Now try another viewer. Most Firestorm users keep a copy of the SL Viewer installed for testing purposes. AND... if you do have to go to the Lab for help, they will insist you use the SL Viwer to get their help.

Also, strip your avatar to the basic nude Classic avatar.

These steps will reveal or eliminate most of the possible problems on your side. Also, they provide info needed by the Lab to help.

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 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 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.

 

OR....JUST A THOUGHT

The Lindens could fix the bugs in their viewer and you will stop crashing.

Which they did, and a new patch dropped.

 

[Adamburp Adamczyk]

so it worked fine with another avi just not this specific one?

sounds like an issue with something you're wearing, so I'd try the following.

Open the viewer (do NOT log in), turn off RLV (if not using the LL viewer).

Clear your cache, and close the viewer.

Open the viewer again, but log into a specific region - Baronial Castle.  Scripts are turned off here, so it's a good place to reload your inventory.

After your inventory has reloaded, change your entire outfit.

Then try and teleport to any other region, and see if this has fixed it.

Edited December 24, 2023 by Adamburp Adamczyk

[Arielle Popstar]

12 hours ago, Prokofy Neva said:

OR....JUST A THOUGHT

The Lindens could fix the bugs in their viewer and you will stop crashing.

Which they did, and a new patch dropped.

 

And adding a thought to your thought, it would be wonderful if the Lindens had an inworld support group for their own viewer so one does not have to come to the forum to find solutions for the "Official SL Viewer".

[JUSTUS Palianta]

Hey no complaining about the viewer, you have new shiny PBR.

[JUSTUS Palianta]

Try using firestorm like all the cool kids. ❤️

[Sid Nagy]

37 minutes ago, JUSTUS Palianta said:

Try using firestorm like all the cool kids. ❤️

You must be a true believer, if you think Firestorm is the snake oil solution for every issue that is SL related. 

Edited December 26, 2023 by Sid Nagy

[Arielle Popstar]

14 minutes ago, Sid Nagy said:

You must be a true believer, if you think Firestorm is the snake oil solution for every issue that is SL related. 

I'm quite convinced that had it not been for Firestorm's inworld support, SL as a whole would never have lasted as long as it has nor as successfully.

[Sid Nagy]

43 minutes ago, Arielle Popstar said:

I'm quite convinced that had it not been for Firestorm's inworld support, SL as a whole would never have lasted as long as it has nor as successfully.

But Firestorm is not the snake oil solution for everything.
It has it's issues too, more than once.

It is a bit strange if someone says they have a problem with the engine of their Ford, to give as the solution: "Buy a Toyota".

Edited December 26, 2023 by Sid Nagy

[RhiannaReach]

Thank you everyone for the suggestions, have tried quite a few of them to no avail but I have submitted a ticket.Tried firestorm and my avi looked like BOM had been switched off and then it disconnected. Don't have time to get undressed I'm disconnected with 10 secs. So I'll just have to wait and see I guess, oh and the sim has been restarted so it's not that. Thank you again. 

[RhiannaReach]

Thank you everyone and without reading them all again, someone mentioned something I was wearing. Because I didn't have time to take things off I relied on LL helping. They have been really good and finally managed to 'undress' my avi and I apparently stayed logged in. So now I need to very slowly 'make my avi' again and take note of what I am wearing etc. I'm very grateful for ALL comments and very grateful to the support team at LL for their help. Rhianna xxxx

[Bree Giffen]

New pickup line spreading like wildfire in SL. Hey I'm tech support and I need to get you naked to make sure you can log in correctly.