Jump to content
  • 0
Sign in to follow this  
IMGypsy

Firestorm keeps crashing and only since I moved to Canada

Question

  • 0

I doubt it's the move to Canada that's caused this.

First thing I'd check is your internet connection,   How fast is it, and what's the ping time like?    If you're using a wireless connection, you should be aware that SL isn't really designed for wireless -- sometimes wireless works fine, but other times it just keeps crashing.   Switch to a cable connection if possible.

  • Like 2

Share this post


Link to post
Share on other sites

5 answers to this question

Recommended Posts

  • 0

I doubt it's the move to Canada that's caused this.

First thing I'd check is your internet connection,   How fast is it, and what's the ping time like?    If you're using a wireless connection, you should be aware that SL isn't really designed for wireless -- sometimes wireless works fine, but other times it just keeps crashing.   Switch to a cable connection if possible.

  • Like 2

Share this post


Link to post
Share on other sites
  • 0

Relize it wasn't the move but ..... I have used wireless before in Montana and elsewhere with no issues at all. Is it possible when I did a clean re-install of both SL viewer & Firestorm that a file got removed, corrupted or? Like I say never have had an issue with using wireless no matter where I have lived until I got here.

Share this post


Link to post
Share on other sites
  • 0

As I said, sometimes wireless works fine. Sometimes it's hopeless. I don't use it myself for SL but a friend of mine tells me she can run SL on wireless without problems in some rooms in the house but it's hopeless in others. Sounds to me that you've been fortunate so far, but in your new home you're not so lucky.

 

Maybe try repositioning the router?

Share this post


Link to post
Share on other sites
  • 0

I agree with Innula. Not likely your location that causees the crash.

But, I doubt a lousy connection is crashing the viewer.

You need to tell us more about what happens when you crash. Do you get an error message, crash to desktop, viewer poofs, locks up... what?

Also when asking any tech question that involves you viewer and computer include the info from HELP->ABOUT...

You can start troubleshooting from here: http://wiki.phoenixviewer.com/firestorm_troubleshooting

 

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 viewers starts. You’ll find the logs in:

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

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

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×
×
  • Create New...