SL 1.12.2(7) crashes on MacBook Pro

The latest version of SL, from today's update, won't even fully launch on my MacBook Pro. It crashes right after it starts drawing the first window. This is *not good*! (I tried this after seeing someone mention in the blog that they had this problem.)

MB Pro 1.83, 128M VRAM, 2 GB RAM

installed it completely w/o auto update... after the release notes it goes to white screen and crash report.

macbook pro, 1.83, 1,024 ram, osx 10.4.8

OK, I had an old version on my other MacBook Pro (same setup -- only 1 GB RAM). I let SL do the update. It's working there. What didn't work was downloading the latest version manually. Next step, gonna try copying the working app over manually.

i tried this, too, seraph, the auto update didn't work so i installed it manually. could not get any worse

cabac

OK, since it worked on one computer, I tried something. Background: I deleted the old Application Support folder for SL and the SL preferences file prior to starting all this.

1. Reinstalled 1.12.1(13) & launched it.
   
2. Since it successfully launched, after having rebuilt the deleted folder and file mentioned above, on a hunch, I quit.
   
3. Launched 1.12.2(7) -- it worked!
   

Looks like the latest version may not be able to properly build the necessary support folders.

any idea where to get the prior release? it's not available anymore, checked versiontracker already.

tyvm

To confirm the problem & fix, I did the following:

1. Renamed the ~/Library/Application Support/Second Life folder
   
2. Launched SL 1.12.2(7)
   
3. Crashed.
   
4. Deleted the newly created SL folder
   
5. Renamed the old folder back to its original name
   
6. Launched SL 1.12.2(7)
   
7. It works!
   

Note: The working folder was created by launching the last version of SL.

I am dead in the water. I get the same results as others--bug fix screen, spectacular crash. I'm missing classes, people!

The first time I installed the upgrade, I let SL do it, then I completely uninstalled and reinstalled the new version manually. Nothing. I uninstalled the new version and installed the old version then let SL do the upgrade again and nothing. Then I emptied my trash without realizing I'd already trashed the old installer, so I can't try the workarounds that have been posted here.

Any help very gratefully appreciated.

i have no idea what the hell was going on but without doing anything, just waiting, reading the blog, the posts... starting sl again - and it worked! no crashes, good performance...

a miracle. whatever. it works, that's the good news.

cu in sl.

cabac

I'm going to check this out soon when I have a chance, thx for pointing me here, CaBaC.

Yet another followup -- this problem does not occur on a PowerBook G4 that I tried. Only the MacBook Pro. And sometimes deleting just the Application Support folder doesn't trigger the problem -- you need to delete the preferences, too. I can't speak as to how it is with other Intel-based Macs.

If anyone at LL wants to discuss this further with me, you can PM, IM, or even email me at my address on record.

I did what Seraph suggested here:



The key is to install the new version of SL into a different location (don't simply drag it to your Apps folder, replacing the old version).

A colleague of mine had the old installer.

Thank you!! See you in-world.

Ah, should have mentioned -- don't delete the other SL app. Either rename it or run it from a different location. Note that on the Mac, SL will run from anywhere -- it doesn't have to be in the Apps folder. I've run it from the desktop and a USB key in the Apple Store.

You should be careful about using the USB key. Aside from the horrible I/O, Second Life uses a non-secure method of saving your details. If you aren't careful what you type when you log-in you can sometimes leave your password behind in plain text on the machine.

I'd still need the old version, correct?

If so, where do I find it?

Trying again with current version.

I too get the crasjh on start up.... i use iMac 24" intel with gforce 7600 ....


What a bore......

Crash on Macbook Pro 15"
2.0Ghz Core Duo
2.0Gb RAM
OSX 10.4.8

Crash on MacPro
Dual 2.66GHz Xeon
2.0Gb RAM
ATi X1900XT
OSX 10.4.8

It's been crashing every time I try to launch it on my intel iMac. However, when I moved it to the desktop it launched right away.

This worked for me as well and no need for the old version.

-Steve

I can add here that the new OS X version is more unstable than the previous version on my Powerbook. Previous version worked like a dream. New version has crashed, and frequently my av doesn't respond to any of the keys for movement and i cannot move, especially after using close-up and rotate on the camera. Sometimes fly-stop fly resolves it or a relog required. (Caches cleared). Might try the remedies suggested here to see if that works but generally I'm unhappy that the update seems to be more unreliable than the previous version.

PowerBook G4 (PowerPC) 1.67 GHz, 2 GB, ATI Mobility Radeon 9700: (AGP 128mb VRAM) running OS 10.4.7

It starts and runs OK on my macbook pro but crashes everytime I try to launch the help screen. As a complete newb I really need that tool! Anyone have a workaround for that kind of issue?

I have no problems with the software on my Intel Mac book Pro with 2 gigs ram. Everything thing seems to be working fine.

Hi again! I'm back -- just wanted to confirm that "F1 Help" crashing on the Mac version of Second Life 1.12.2.7 *is* a known issue. It's been resolved internally, so look for a fix soon.

Also, while I didn't crash upon startup like some of you are reporting (I'm on an Intel MacBook Pro), we do have another issue where changing bumpmapped texture options to "brightness" or "darkness" will crash you. (Edit: we only know of this happening in an internal build, so it shouldn't affect you -- thx Milo.)

In addition, I'm going to check with our Quality Assurance Team to see what more info we have concerning these.

For those of you still crashing, please submit your crash reports. Have Edit menu > Preferences > General tab's "Crash reports" set to send.

Please also IM me inworld that you posted a crash report so we can focus on those -- thanks!