How to disable Crashreporter, I can't launch SecondLife

Every time I launch SecondLife, it kicks into Crashreporter. And when I either send the report or cancel the report, it never goes back to SecondLife.

I re-download and reinstall SL, but nothing works. I tried to delete the preference files but nothing works either.

I'm using Mac OS X, how can I delete the crash log files, and disable Crashreporter so I can launch SL?

Under your user, go to Library > Application Support > Second Life. There are the things to delete. Oh, and good luck with Crash Reporter. Whenever I tried to use it, it crashed.

When you reinstalled SL, did you do a complete uninstall before reinstalling it?

I figured it out. When I manually deleted the caches files, then it launched without redirecting it to Crashreporter.

Ooooh ooh! Good! I just installed SL on a friend's computer who wants to try it out...but it does the same. Open to the login page and crashes before we even get the chance to type his user name.

** Where can I find the cache files?

I believe you can see the path to the cache files in the Preferences dialog on the Network tab.

On a default windows installation of SL, they are at:

"C:\Documents and Settings\YOUR-USERNAME-GOES-HERE\Application Data\SecondLife\cache"

or you can use the %username% system variable for the username:

"C:\Documents and Settings\%username%\Application Data\SecondLife\cache" .

You can do Start, Run, and paste in "C:\Documents and Settings\%username%\Application Data\SecondLife\cache" and press enter on a default windows install of SL and that will put you in the cache folder one most Windows user's systems.

Thank you for posting the stuff after this line.. the problem is that I don't even get to SEE the preferences dialog or anything.. The SL login window opens... then BAM! Crash.

I also note that the crash reporter looks different from the one on my system. It writes about why we should send a report blah blah blah... mine just says (basically) "You crashed, wanna send a report?"

I tried installing the current version, the previous version AND also the 'preview' version... full uninstall before each install... nope, all the same.

I'll try clearing the cache like suggested, but I don't really think there will BE anything in the cache. It hasn't even had the user name typed in yet. I'll also check out the library thing... wish me luck!

Aaaaah!!! I tried deleting the cache... nope, didn't help at all.

If I send a support ticket to LL, do you think they will respond since he is not a paying account?? ~_~ I'm going to try anyway.

"he SL login window opens... then BAM! Crash."

Are you starting SL from the shortcut that SL creates or from one that you made in the past? If you are using an old one, try using the one that the SL install creates.

If you are using the standard version of SL, you might try using the release candidate. It appears to still work for me, and seems as stable as the last regular version I used was.

I wonder what would happen if you renamed the crash reporter so it didn't get to execute. Probably something bad.


On a default install of SL on Windows, the settings file is stored in
C:\Documents and Settings\%username%\Application Data\SecondLife\FirstName_LastName

As an example, mine is located in
On a default install of SL on Windows, the settings file is stored in
C:\Documents and Settings\%username%\Application Data\SecondLife\suezannec_baskerville

The file is called settings.xml.

If you have done uninstalls, that file should have been deleted, but it can't hurt to make sure.

The log files are on a default Windows installation are stored in the folder

C:\Documents and Settings\%username%\Application Data\SecondLife\logs

The file that has the running record of events is called SecondLife.log .

It's a text file that you can open with notepad. You might try copying the last ten or twenty lines from that and putting them here.

OK, I'll give it a whirl - deleting the crash reporter that is... I've sent a support ticket to LL asking for help.

I've done uninstalls, cache deletion, tried the candidate, current AND older versions. Disabled anti-virus, firewalls.. everything I can think of. It still crashes.

I'd post the log, but I'm not there atm. I'm at work for the next... 10 1/2 hours.. (Wow, I just realised I work 12 1/2 hours on Fridays ~_~).. I remember from reading it before that the last line was something like 'Initialize LoginMenu' or something ~_~ (Looking through my own log here, I think it's " login_show: Initializing Login Screen" then that's it.. nothing written after that..

Any progress on this?

Any Mac users able to offer any advice?

Have you filed a support ticket?

No progress... we've gone through now and checked that relevant drives are all up to date. Still nothing helping.

I filed a support ticket yesterday, but no reply yet.

Here is the last section of the secondlife.log
---------------------------------------------------------
2007-09-22T05:53:20Z INFO: WinMain: Viewer Digest: a87624d3-9a34-a2fa-8e8f-2859d022c811
2007-09-22T05:53:20Z INFO: LLVoiceClient:etState: entering state stateDisabled
2007-09-22T05:53:20Z INFO: LLVoiceClient:witchChannel: called in state stateDisabled with uri ""
2007-09-22T05:53:20Z INFO: LLViewerThrottleGroup::dump: Resend: 75
2007-09-22T05:53:20Z INFO: LLViewerThrottleGroup::dump: Land: 85
2007-09-22T05:53:20Z INFO: LLViewerThrottleGroup::dump: Wind: 17
2007-09-22T05:53:20Z INFO: LLViewerThrottleGroup::dump: Cloud: 17
2007-09-22T05:53:20Z INFO: LLViewerThrottleGroup::dump: Task: 223
2007-09-22T05:53:20Z INFO: LLViewerThrottleGroup::dump: Texture: 223
2007-09-22T05:53:20Z INFO: LLViewerThrottleGroup::dump: Asset: 110
2007-09-22T05:53:20Z INFO: LLViewerThrottleGroup::dump: Total: 750
2007-09-22T05:53:20Z INFO: idle_startup: Initializing messaging system...
2007-09-22T05:53:20Z INFO: LLTemplateParser::LLTemplateParser: ### Message template version 2 ###
2007-09-22T05:53:20Z INFO: start_net: attempting to connect on port 0
2007-09-22T05:53:21Z INFO: start_net: connected on port 3013
2007-09-22T05:53:21Z INFO: start_net: startNet - receive buffer size : 400000
2007-09-22T05:53:21Z INFO: start_net: startNet - send buffer size : 400000
2007-09-22T05:53:21Z INFO: start_messaging_system: Message template version matches prehash version number
2007-09-22T05:53:21Z INFO: LLMessageConfigFile::loadFile: Loading message.xml file at C:\Program Files\SecondLife\app_settings/message.xml
2007-09-22T05:53:21Z INFO: LLMessageConfigFile::loadCapBans: 22 ban tests
2007-09-22T05:53:21Z INFO: LLMessageSystem:etMessageBans:
2007-09-22T05:53:21Z INFO: LLMessageSystem:etMessageBans: no messages banned
2007-09-22T05:53:21Z INFO: LLMessageConfig::initClass config file C:\Program Files\SecondLife\app_settings/message.xml
2007-09-22T05:53:21Z INFO: LLXferManager:etAckThrottleBPS: LLXferManager ack throttle min rate: 2.66667e+006
2007-09-22T05:53:21Z INFO: LLXferManager:etAckThrottleBPS: LLXferManager ack throttle actual rate: 2.93333e+006
2007-09-22T05:53:21Z INFO: LLXferManager:etAckThrottleBPS: LLXferManager ack throttle min rate: 8000
2007-09-22T05:53:21Z INFO: LLXferManager:etAckThrottleBPS: LLXferManager ack throttle actual rate: 150000
2007-09-22T05:53:21Z INFO: LLAssetStorage:etUpstream: AssetStorage: Setting upstream provider to 0.0.0.0:0
2007-09-22T05:53:21Z INFO: idle_startup: Initializing embedded web browser...
2007-09-22T05:53:23Z INFO: LLAudioEngine_FMOD::init() initializing FMOD
2007-09-22T05:53:23Z INFO: LLAudioEngine_FMOD::init() FMOD initialized correctly
2007-09-22T05:53:23Z INFO: idle_startup: Initializing Window
2007-09-22T05:53:23Z INFO: login_show: Initializing Login Screen

------
and that's it

/me screams, sick of waiting nigh on 20 minutes for 'initiating chat' to actually do what it says... ><

Now where's that thread about the age verification being about LL just throwing the job to us... I guess support is another thing thrown to the users.

Have you filed a Jira issue?

Also, do you have a blog? If so you might post your story there. Then copy and paste that post into a post at the sluniverse forums and the slexchange forums and any other sl forums that get much traffic.

If you are running a Mac, you could post in the Mac forum with a link to this thread.

I see in the logs that it appears the crash happens shortly after loading FMOD. FMOD is part of the sound system that SL uses. You can start SL without loading FMOD.

There's a page at http://lslwiki.net/lslwiki/wakka.php?wakka=NewView that shows command line options for Second Life.

To use these command line options on a mac,

Right-click or control click on the Second Life icon and choose 'Show Package Contents'.

Browse from there to Contents -> Resources.

Look for a file called 'arguments.txt'. If it does not exist, create it.

Inside this file add any command line arguments you want (same ones that work for Windows).

You might try -safe , which is supposed to reset preferences and run SL in "safe mode", whatever that might be.

You might try -nofmod or -nosound or -noaudio .

I'm just guessing on this stuff.

If you haven't tried disabling your anti-virus, firewall, anti-spy, anti-malware, etc. software, you could give that a try.

There is a Jira issue that might be related: http://jira.secondlife.com/browse/VWR-1926 .

In the Mac, all the support files of SecondLife are located in your home directory in this path:

Macintosh HD/yourusername/Library/Application Support/SecondLife/

You will find the folder for all the SL support files, such as "cache", "logs", "user_settings", "browser_profile", etc.

Delete them all, and you should be able to start SecondLife without kicking into CrashReporter. SecondLife will recreate these files automatically once you deleted them.

The reason why it caused the above problem is when you install and copy files from another machine, it copied all the support files from the original files too, and SecondLife is very confused because it thinks you were still using the original machine in the cache files but the old computer is not there any more, so it kept trying to tell you something is wrong with that!

So it's a bug in SecondLife, they should check the validity of the cache files before trusting them and should trash them if they are invalid.