2 Replies Latest reply: Feb 10, 2013 8:44 AM by Solarflare79
Solarflare79 Level 1 (0 points)

Any 32 bit application I try to run in OSX 10.8.2 crashes.

64bit applications launch normally with no problems.

Sample of error message - which I get with ANY 32 bit application.


Process:     Google Chrome [390]
Path:        /Programs/Google Chrome.app/Contents/MacOS/Google Chrome
Identifier:  com.google.Chrome
Version:     23.0.1271.101 (1271.101)
Code Type:   X86 (Native)

Parent Process:  launchd [147]

User ID:     501


Date/Time:   2013-02-10 10:00:52.851 -0600
OS Version:  Mac OS X 10.8.2 (12C54)

Report Version:  10


Interval Since Last Report:      3461 sec
Crashes Since Last Report:       37

Per-App Interval Since Last Report:  257312 sec

Per-App Crashes Since Last Report:   5

Anonymous UUID:                  5BB966E8-5957-D0C6-BB9E-765C6E524032


Crashed Thread:  0  Dispatch queue: com.apple.main-thread


Exception Type:  EXC_BAD_ACCESS (SIGBUS)

Exception Codes: 0x000000000000000a, 0x000000009c100e19


VM Regions Near 0x9c100e19:

__LINKEDIT         000000008ff50000-000000008ff63000 [   76K] r--/rwx SM=COW  /usr/lib/dyld
--> Submap             0000000090000000-00000000ac000000      r--/rwx machine-wide submap
mapped file        0000000090000000-0000000090007000 [   28K] r-x/r-x SM=COW  Object_id=3380a720

OS X Mountain Lion (10.8.2)
  • den.thed Level 7 (25,980 points)

    I don't use Google Crome, but it looks like you need to either update Chrome or download the latest version from > Chrome Browser  which is something like v24.0.1313.57

  • Solarflare79 Level 1 (0 points)

    Shortly after I made my post, I was able to resolve the issue using information provided from the link below.




    For some reason, after rebooting in safe mode I was able to launch 32 bit applications again.


    When looking into my issue I founda few articles with people reporting the same problem, except they were reporting the issue for specific applications. I noticed in all the posts I read that the one consistency was the code type being x86 (native) 32bit applications.


    Figured I'd update this in case anyone else has been having similar issues.