Jump to content

"The Application [Nearly Everything] Quit Unexpectedly"


cizin456
 Share

15 posts in this topic

Recommended Posts

I just installed OS X and so many apps don't work that it baffles me. Right after I click on them, maybe it bounces once, it will display the message. Aperature, Toast, Gumby 50c, Quicktime, are ones i discovered are not working so far. Presumably, future software wont work either... The error messages are quite lengthy and i don't know how to post in a code box but heres the beginnings to one. By the way I'm running Leo4All v2 10.5.2 and I'll post specs if needed...

 

 

Process: Aperture [447]

Path: /Applications/Aperture.app/Contents/MacOS/Aperture

Identifier: com.apple.Aperture

Version: ??? (???)

Build Info: Aperture-802050200~3

Code Type: X86 (Native)

Parent Process: launchd [96]

 

Date/Time: 2008-06-15 04:22:07.640 -0400

OS Version: Mac OS X 10.5.2 (9C7010)

Report Version: 6

 

Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x000000004a07ab58

Crashed Thread: 0

 

Thread 0 Crashed:

0 com.apple.opengl 0x93f8a04f CGLDescribePixelFormat + 1263

1 com.apple.opengl 0x93f8a0c1 CGLDestroyContext + 33

2 com.apple.Aperture 0x00003e43 0x1000 + 11843

3 com.apple.Aperture 0x00003ffd 0x1000 + 12285

4 com.apple.Aperture 0x000040d3 0x1000 + 12499

5 com.apple.Aperture 0x00003652 0x1000 + 9810

6 com.apple.Aperture 0x00003579 0x1000 + 9593

 

Thread 1:

0 libSystem.B.dylib 0x9139da46 semaphore_timedwait_signal_trap + 10

1 libSystem.B.dylib 0x913cfdaf _pthread_cond_wait + 1244

2 libSystem.B.dylib 0x913d1633 pthread_cond_timedwait_relative_np + 47

3 com.apple.Foundation 0x950694fc -[NSCondition waitUntilDate:] + 236

4 com.apple.Foundation 0x95069310 -[NSConditionLock lockWhenCondition:beforeDate:] + 144

5 com.apple.Foundation 0x95069275 -[NSConditionLock lockWhenCondition:] + 69

6 com.apple.proxtcore 0x008e10a3 describeMsgCode + 6334

7 com.apple.proxtcore 0x008d0a83 threadSuspendedCountDiff + 7367

8 com.apple.Foundation 0x950235ad -[NSThread main] + 45

9 com.apple.Foundation 0x95023154 __NSThread__main__ + 308

10 libSystem.B.dylib 0x913cec55 _pthread_start + 321

11 libSystem.B.dylib 0x913ceb12 thread_start + 34

 

Thread 2:

0 libSystem.B.dylib 0x913a4bce __semwait_signal + 10

1 libSystem.B.dylib 0x913cf8cd pthread_cond_wait$UNIX2003 + 73

2 libGLProgrammability.dylib 0x96b44332 glvmDoWork + 162

3 libSystem.B.dylib 0x913cec55 _pthread_start + 321

4 libSystem.B.dylib 0x913ceb12 thread_start + 34

 

Thread 0 crashed with X86 Thread State (32-bit):

eax: 0x00000000 ebx: 0x93f8a2db ecx: 0x00000001 edx: 0x012af000

edi: 0x01851274 esi: 0x00000000 ebp: 0xbffff928 esp: 0xbffff8e0

ss: 0x0000001f efl: 0x00010246 eip: 0x93f8a04f cs: 0x00000017

ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037

cr2: 0x4a07ab58

 

Thanks in advance!

CiZiN

Link to comment
Share on other sites

That's bizarre. No need to post all the error messages or crash reports if they're all similar. It could be a 32/64 bit mixup somehow? I don't have 64-bit hardware but I notice this

 

Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x000000004a07ab58

 

shows a kernel address that's 64 bits. Does this show anything in a terminal session?

 

sudo nm /mach_kernel | grep -i 4a07ab58

 

That's your "bad address" but normally that error happens when the address is 0. 4a07ab58 looks like a valid memory address. Can you boot another OS on the machine? If so that would rule out bad RAM.

Link to comment
Share on other sites

I cant execute because it says "sudo: nm: command not found"

Oh, and i notice they each have different errors which cant be good.. quicktime has

 

Exception Type: EXC_BAD_ACCESS (SIGBUS)

Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000

Crashed Thread: 0

 

And Gumby 50c has

 

Exception Type: EXC_BAD_INSTRUCTION (SIGILL)

Exception Codes: 0x0000000000000001, 0x0000000000000000

Crashed Thread: 0

 

Toast has

 

Exception Type: EXC_BAD_ACCESS (SIGSEGV)

Exception Codes: KERN_INVALID_ADDRESS at 0x00000000b5b5b5b5

Crashed Thread: Unknown

 

I am assuming this section of the problem details is the important part. For quicktime and Gumby it seems you are right when you said "but normally that error happens when the address is 0" since its 0x0000000000000000

Could this mean bad ram? Oh and this PC used to run Vista x64 until about a month ago, so presumably it still can run another OS.

 

Edit: Need Xcode to do "nm"

Link to comment
Share on other sites

If there was no output from the command then it means nothing, unfortunately. What "nm" does is extract symbols and their addresses from a file. If the address was at the very start of a function it would report the name of that function. When there's no symbol defined at the address, well... you don't get any output.

 

It looks like it's not a common address that's failing.

 

Just to eliminate the hardware, I would pop out the RAM sticks and put them back in again making sure they are seated firmly. Then if the problem was still there I would boot another OS just to see if it works. You can download a 1-CD Linux Live CD image that you can boot from that will exercise the hardware without needing to technically "install" it onto any hard disk or partition. If, that is, you have access to another machine where you can burn a CD.

 

To tell you the truth, however, I don't think it's the hardware. But I would eliminate that possibility right away so you don't have lingering doubt. You could debug for a week and you'd always have in the back of your mind, "Is my RAM bad?" If it can run another OS then you eliminate that possibility.

Link to comment
Share on other sites

I reseated all of the RAM sticks and made sure they were in firmly. I didn't have a linux CD on hand but i did have a Memtest86 CD i ran for 22+ hours without any errors. I swapped out my 7800 GT 256 MB for an identical just to make sure it wasn't a video card problem. (This PC used to run two in SLI, so i happened to have a spare.) But what I did notice, was that all the apps that crashed crashed (all the above mentioned, and Safari and Preview) had these lines the same

 

Thread 0 Crashed:
0   com.apple.opengl              	0x93f8a04f CGLDescribePixelFormat + 1263

 

This caused me to think...Is this a video card driver making these apps crash?

Link to comment
Share on other sites

I installed JaS 10.4.8 distro because i had it on hand... Does that count? Everything worked just fine. Does this indicate that it is in-fact a software, not a hardware, problem? If so can you help me solve this problem..

Link to comment
Share on other sites

  • 5 weeks later...

Same problem on Neverwinter Nights 2...driving me nunts!

 

Only happens with this app (so far)....

 

Have Vista on another hd and it works flawlessly...so not RAM.

 

My son has nearly the same hardware on 10.5.2 and NWN2 works like a champ...I have 10.5.4. When I upgraded is it possible that some mod'd kext got deleted and now certain programs won't run?

 

Process: Neverwinter Nights 2 [191]

Path: /Applications/Neverwinter Nights 2/Neverwinter Nights 2.app/Contents/MacOS/Neverwinter Nights 2

Identifier: com.aspyr.NWN2

Version: ??? (???)

Code Type: X86 (Native)

Parent Process: launchd [106]

 

Date/Time: 2008-07-23 01:06:25.324 -0400

OS Version: Mac OS X 10.5.4 (9E17)

Report Version: 6

 

Exception Type: EXC_BAD_INSTRUCTION (SIGILL)

Exception Codes: 0x0000000000000001, 0x0000000000000000

Crashed Thread: 0

 

Thread 0 Crashed:

0 com.aspyr.NWN2 0x0001e945 0x1000 + 121157

1 ??? 0x0096f929 0 + 9894185

2 dyld 0x8fe12e76 ImageLoaderMachO::doModInitFunctions(ImageLoader::LinkContext const&) + 246

3 dyld 0x8fe0e723 ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int) + 307

4 dyld 0x8fe0e809 ImageLoader::runInitializers(ImageLoader::LinkContext const&) + 57

5 dyld 0x8fe04102 dyld::initializeMainExecutable() + 146

6 dyld 0x8fe07b5f dyld::_main(mach_header const*, unsigned long, int, char const**, char const**, char const**) + 2975

7 dyld 0x8fe01872 dyldbootstrap::start(mach_header const*, int, char const**, long) + 818

8 dyld 0x8fe01037 _dyld_start + 39

 

Thread 0 crashed with X86 Thread State (32-bit):

eax: 0x0001e945 ebx: 0x0097011a ecx: 0x00000000 edx: 0x0001e843

edi: 0x00000001 esi: 0x000014c0 ebp: 0xbfffe118 esp: 0xbfffe0ec

ss: 0x0000001f efl: 0x00010246 eip: 0x0001e945 cs: 0x00000017

ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037

cr2: 0x0001e945

Link to comment
Share on other sites

  • 2 months later...

I have the same issue with everything.

It's usually when I start multi tasking, but it mainly just happens randomly.

And games work great on here, if they're not older games.

 

If anyone knows how to fix this bug, PLEASE someone reply.

I'm thinking different SMBios? Or Kernel maybe?

Link to comment
Share on other sites

  • 1 month later...
  • 1 year later...

same problem me too!!!

 

when i'm trying to open Finder Preferences and at the boot 2 times the same log error....

 

i've tried this but don't works for me!

________________________________________________________________________________

________

To correct the error:

1) Log in as an Administrator.

2) Create a new user account, called NewUser.

[The name isn't important, because you're going to delete this account when we're done].

2b) If the affected user account is not an administrator account, go ahead and make it one. You can revoke this privilege later, but it will make things easier for now.

3) Log out, and log back in as NewUser.

[This will initialize the account and create undamaged preferences.]

4) Log back out, and log in again as the user affected by the crashed (who, according to step 2b, is an Administrator).

5) Launch the "Terminal" application, located in /Applications/Utilities/

6) Type the following command (for all of the following, copy and paste):

cd ~/Library/Preferences/

7) Type this command:

rm .GlobalPreferences.plist

8) Type this command:

sudo cp /Users/NewUser/Library/Preferences/.GlobalPreferences.plist .

[it will ask for an administrator password to allow you to log in as root for this action]

9) Type this command -- DON'T COPY-PASTE THIS ONE! YOU NEED TO PUT YOUR OWN USERNAME:

sudo chown USERNAME .GlobalPreferences.plist

10) Log out.

10b) If you enabled Admin access on an account that shouldn't have it, log back in as an Administrator and disable that Admin access.

11) Delete the NewUser account.

12) Log out, and log in to the affected acount.

________________________________________________________________________________

________

 

any ideas?

Link to comment
Share on other sites

 Share

×
×
  • Create New...