Jump to content

MAC crash on upload of image - updated with crash log


Streex Foxtrot
 Share

Recommended Posts

I can go to my invantory select upload and select my image, but before the preview is even brought up...my mac pinwheels, and opens a crash logger closing out SL. My SL is up to date as of yesterday, I don't know why this is happening, I use the LL viewer, I do not use a 3rd party viewer. After the crash it takes forever to log back in! JUST AGES! 

 I should state this is with JPGs, PNGs, and TARGAS.....everything I've tried. I'm not uploading mesh, nor am I uploading large files. 

I'm desperate for this to stop, it's been going on for months and I can't use SL without being able to upload. This is effectively killing my business ....

 

Here's my info:

Second Life 3.6.12 (284506) Dec  3 2013 21:37:58 (Second Life Release)

CPU: Intel(R) Core(TM) i5-2415M CPU @ 2.30GHz (2300 MHz)
Memory: 8192 MB
OS Version: Mac OS X 10.8.5 Darwin 12.5.0 Darwin Kernel Version 12.5.0: Sun Sep 29 13:33:47 PDT 2013; root:xnu-2050.48.12~1/RELEASE_X86_64 x86_64
Graphics Card Vendor: Intel Inc.
Graphics Card: Intel HD Graphics 3000 OpenGL Engine

OpenGL Version: 2.1 INTEL-8.16.74

libcurl Version: libcurl/7.21.1 OpenSSL/0.9.8q zlib/1.2.5 c-ares/1.7.1
J2C Decoder Version: KDU v7.0
Audio Driver Version: FMOD Ex 4.44.12
Qt Webkit Version: 4.7.1 (version number hard-coded)
Voice Server Version: Vivox

Built with GCC version 40201
Packets Lost: 28/4417 (0.6%)

 

CRASH LOG: 

Process: Second Life [20781]
Path: /Applications/Second Life Viewer.app/Contents/MacOS/Second Life
Identifier: com.secondlife.indra.viewer
Version: Second Life version 3.6.12.284506 (3.6.12.284506)
Code Type: X86 (Native)
Parent Process: launchd [149]
User ID: 501

Date/Time: 2013-12-18 18:48:01.599 -0500
OS Version: Mac OS X 10.8.5 (12F45)
Report Version: 10

Interval Since Last Report: 130834 sec
Crashes Since Last Report: 1
Per-App Interval Since Last Report: 38778 sec
Per-App Crashes Since Last Report: 1
Anonymous UUID: 5315F385-482D-783A-BB07-1AF7AAEFC48E

Crashed Thread: 0

Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000

Application Specific Information:
dyld: launch, loading dependent libraries

Dyld Error Message:
Library not loaded: @executable_path/../Resources/libcollada14dom.dylib
Referenced from: /Applications/Second Life Viewer.app/Contents/MacOS/Second Life
Reason: image not found

Binary Images:
0x1000 - 0x2226ff3 +com.secondlife.indra.viewer (Second Life version 3.6.12.284506 - 3.6.12.284506) <6E7D6FAE-F9AF-3436-A681-4961D104C5D6> /Applications/Second Life Viewer.app/Contents/MacOS/Second Life
0x8fec7000 - 0x8fef9e57 dyld (210.2.3) <23DBDBB1-1D21-342C-AC2A-0E55F27E6A1F> /usr/lib/dyld

Model: Macmini5,1, BootROM MM51.0077.B10, 2 processors, Intel Core i5, 2.3 GHz, 8 GB, SMC 1.76f0
Graphics: Intel HD Graphics 3000, Intel HD Graphics 3000, Built-In, 512 MB
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1333 MHz, 0x802C, 0x31364A54463531323634485A2D3147344D31
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1333 MHz, 0x802C, 0x31364A54463531323634485A2D3147344D31
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xE4), Broadcom BCM43xx 1.0 (5.106.98.100.17)
Bluetooth: Version 4.1.7f4 12974, 3 service, 21 devices, 3 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: TOSHIBA MK5065GSXF, 500.11 GB
USB Device: hub_device, 0x0424 (SMSC), 0x2513, 0xfd100000 / 2
USB Device: Keyboard Hub, apple_vendor_id, 0x1006, 0xfd130000 / 5
USB Device: USB DISK, 0x090c (Silicon Motion, Inc. - Taiwan), 0x1000, 0xfd133000 / 8
USB Device: Microsoft 3-Button Mouse with IntelliEye(TM), 0x045e (Microsoft Corporation), 0x0040, 0xfd131000 / 7
USB Device: Apple Keyboard, apple_vendor_id, 0x024f, 0xfd132000 / 6
USB Device: CTH-461, 0x056a (WACOM Co., Ltd.), 0x00d2, 0xfd120000 / 4
USB Device: IR Receiver, apple_vendor_id, 0x8242, 0xfd110000 / 3
USB Device: hub_device, 0x0424 (SMSC), 0x2513, 0xfa100000 / 2
USB Device: Blue Snowball, 0x0d8c (C-MEDIA ELECTRONICS INC.), 0x0005, 0xfa120000 / 4
USB Device: BRCM20702 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0xfa110000 / 3
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8281, 0xfa113000 / 6

Link to comment
Share on other sites

Hi Streetx,

Are you really running Version 2? I didn't think old viewers were able to log into SL anymore. If you really are running V2, I suggest you upgrade to the current 3.6.x.

I have had crashing problems in the past, particularly after updates and usually on launch. I've found that tossing the viewer's "Saved Application State" folder gets things working again. To do that, quit the viewer, then open the system library folder by selecting "Library" from the Finder's "Go" menu, while holding down the "Option" key. From there, go to "Saved Application State" and locate the folder "com.secondlife.indra.viewer.savedState" (or something else that seems related to the viewer in question) and toss it in the trash. Launch the viewer.

If that doesn't work, try a clean install. Instructions for doing that are here...

http://community.secondlife.com/t5/English-Knowledge-Base/How-to-uninstall-and-reinstall-Second-Life/ta-p/1375231/comment-id/408

I've added more Mac specific instructions on that page, including those given above.

Good luck!

Link to comment
Share on other sites

No, she hasn't misread. SL's latest viewer generation is V3. So if you are still in a V2 then ... oh well, I guess you can't even log in. Anyway, waht worries me more is your onboard graphics chip. LL doesn't support Intel HD stuff. But since you're on a Mac you're trapped with what you got. :smileyindifferent:

 

Link to comment
Share on other sites


Orca Flotta wrote:

No, she hasn't misread. SL's latest viewer generation is V3. So if you are still in a V2 then ... oh well, I guess you can't even log in. Anyway, waht worries me more is your onboard graphics chip. LL doesn't support Intel HD stuff. But since you're on a Mac you're trapped with what you got. :smileyindifferent:

 

Yes, she did mis-read.  Please read the specs above it clearly states 3.x. 

Secondly, what do you mean SL does NOT support Intel HD stuff?  Do you have any idea of what you are writing?  I run Intel HD stuff at ~60 FPS on ultra.  Not bad for unsupported HW, eh?

 

Link to comment
Share on other sites

I never use Coverflow...EVER.....I don't know if it can be DISABLED I'll do some research on it to see if it can be perma-disabled. BULK uploads are also effected.

I've established a temporary fix to log into a 3rd party viewer (singularity) but I don't like it's UI. I want to use the SL viewer that doesn't look like the OLD style viewer. 

 

this is the crash log in the hopes we can figure out what is going on: 

Process: Second Life [20781]
Path: /Applications/Second Life Viewer.app/Contents/MacOS/Second Life
Identifier: com.secondlife.indra.viewer
Version: Second Life version 3.6.12.284506 (3.6.12.284506)
Code Type: X86 (Native)
Parent Process: launchd [149]
User ID: 501

Date/Time: 2013-12-18 18:48:01.599 -0500
OS Version: Mac OS X 10.8.5 (12F45)
Report Version: 10

Interval Since Last Report: 130834 sec
Crashes Since Last Report: 1
Per-App Interval Since Last Report: 38778 sec
Per-App Crashes Since Last Report: 1
Anonymous UUID: 5315F385-482D-783A-BB07-1AF7AAEFC48E

Crashed Thread: 0

Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000

Application Specific Information:
dyld: launch, loading dependent libraries

Dyld Error Message:
Library not loaded: @executable_path/../Resources/libcollada14dom.dylib
Referenced from: /Applications/Second Life Viewer.app/Contents/MacOS/Second Life
Reason: image not found

Binary Images:
0x1000 - 0x2226ff3 +com.secondlife.indra.viewer (Second Life version 3.6.12.284506 - 3.6.12.284506) <6E7D6FAE-F9AF-3436-A681-4961D104C5D6> /Applications/Second Life Viewer.app/Contents/MacOS/Second Life
0x8fec7000 - 0x8fef9e57 dyld (210.2.3) <23DBDBB1-1D21-342C-AC2A-0E55F27E6A1F> /usr/lib/dyld

Model: Macmini5,1, BootROM MM51.0077.B10, 2 processors, Intel Core i5, 2.3 GHz, 8 GB, SMC 1.76f0
Graphics: Intel HD Graphics 3000, Intel HD Graphics 3000, Built-In, 512 MB
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1333 MHz, 0x802C, 0x31364A54463531323634485A2D3147344D31
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1333 MHz, 0x802C, 0x31364A54463531323634485A2D3147344D31
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xE4), Broadcom BCM43xx 1.0 (5.106.98.100.17)
Bluetooth: Version 4.1.7f4 12974, 3 service, 21 devices, 3 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: TOSHIBA MK5065GSXF, 500.11 GB
USB Device: hub_device, 0x0424 (SMSC), 0x2513, 0xfd100000 / 2
USB Device: Keyboard Hub, apple_vendor_id, 0x1006, 0xfd130000 / 5
USB Device: USB DISK, 0x090c (Silicon Motion, Inc. - Taiwan), 0x1000, 0xfd133000 / 8
USB Device: Microsoft 3-Button Mouse with IntelliEye, 0x045e (Microsoft Corporation), 0x0040, 0xfd131000 / 7
USB Device: Apple Keyboard, apple_vendor_id, 0x024f, 0xfd132000 / 6
USB Device: CTH-461, 0x056a (WACOM Co., Ltd.), 0x00d2, 0xfd120000 / 4
USB Device: IR Receiver, apple_vendor_id, 0x8242, 0xfd110000 / 3
USB Device: hub_device, 0x0424 (SMSC), 0x2513, 0xfa100000 / 2
USB Device: Blue Snowball, 0x0d8c (C-MEDIA ELECTRONICS INC.), 0x0005, 0xfa120000 / 4
USB Device: BRCM20702 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0xfa110000 / 3
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8281, 0xfa113000 / 6

Link to comment
Share on other sites

  • 1 month later...
  • 1 month later...
  • 3 months later...

This started with me also. I had iCloud turned off, made sure the file was the correct size, and had OpenGL VBO turned off in the graphics preferences (read about it in a different post). Once I had all that done I was finally able to upload an image. woohoo! Messed with it som in game went and ate dinner and an hour later when I tried to upload another image it crashed on me again. Nothing changed. Made the image smaller so the file size wouldn't be as large and still wouldn't.

Link to comment
Share on other sites

  • 6 months later...
  • 2 weeks later...
  • 2 months later...
  • 6 months later...

I Have had the same problem used the fixed on the link provided until today that worked fine.  Now I can not even get to the close the selection window before I crash.  The process does not seem to be able to be saved and am not sure what causes it to go off list.  Is there any other advice on how to correct the issue?

Link to comment
Share on other sites

Was able to find some help from in world group.  The person suggested "the few times they have crashed when uploading images have been when the texture file is buried deep in a nest of folders.... try to keep what you want to upload only a folder or two from the desktop and be sure that its a png or preferrably a tga file.... avoid other formats

I moved the desired image which was a png to a new folder at the top of the nest if you will and the file uploaded with no crashing. 

Link to comment
Share on other sites

  • 1 month later...

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share

×
×
  • Create New...