The Application Quit Unexpectedly

Discussion in 'OS X Mountain Lion (10.8)' started by hellodarren2000, Apr 11, 2013.

  1. macrumors newbie

    Joined:
    Apr 11, 2013
    #1
    Hi. I'm trying to make the game I'm making compatible with Macs but when I click it it seems to load for a few seconds with the name showing at the top, but I then get a "The Application Quit Unexpectedly" error message.

    Any help fixing this appreciated, here's the error log (note I ran into a character limit when posting the full log so had to trim it, let me know if you need the rest):

    Code:
    Process:         Mac_Runner [239]
    Path:            /Users/USER/Desktop/TestGame.app/Contents/MacOS/Mac_Runner
    Identifier:      com.yoyogames.macyoyorunner
    Version:         1.0.1 (1.0.1)
    Code Type:       X86 (Native)
    Parent Process:  launchd [137]
    User ID:         501
    
    Date/Time:       2013-04-11 08:11:19.054 +0100
    OS Version:      Mac OS X 10.8 (12A269)
    Report Version:  10
    
    Interval Since Last Report:          16307 sec
    Crashes Since Last Report:           11
    Per-App Interval Since Last Report:  22 sec
    Per-App Crashes Since Last Report:   3
    Anonymous UUID:                      7EA462F8-C388-4062-BB6A-3DD86E074D9E
    
    Crashed Thread:  3  Dispatch queue: com.apple.root.default-priority
    
    Exception Type:  EXC_BAD_ACCESS (SIGBUS)
    Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
    
    VM Regions Near 0:
    --> __PAGEZERO             0000000000000000-0000000000001000 [    4K] ---/--- SM=NUL  /Users/USER/Desktop/TestGame.app/Contents/MacOS/Mac_Runner
        __TEXT                 0000000000001000-0000000000185000 [ 1552K] r-x/rwx SM=COW  /Users/USER/Desktop/TestGame.app/Contents/MacOS/Mac_Runner
    
    Thread 0:: Dispatch queue: com.apple.main-thread
    0   libsystem_kernel.dylib        	0x9a2697d2 mach_msg_trap + 10
    1   libsystem_kernel.dylib        	0x9a268cb0 mach_msg + 68
    2   com.apple.CoreFoundation      	0x94127cc9 __CFRunLoopServiceMachPort + 185
    3   com.apple.CoreFoundation      	0x9412d6af __CFRunLoopRun + 1247
    4   com.apple.CoreFoundation      	0x9412cd6a CFRunLoopRunSpecific + 378
    5   com.apple.CoreFoundation      	0x9412cbdb CFRunLoopRunInMode + 123
    6   com.apple.HIToolbox           	0x9756c8aa RunCurrentEventLoopInMode + 242
    7   com.apple.HIToolbox           	0x9756c619 ReceiveNextEventCommon + 374
    8   com.apple.HIToolbox           	0x9756c494 BlockUntilNextEventMatchingListInMode + 88
    9   com.apple.AppKit              	0x997ada5a _DPSNextEvent + 724
    10  com.apple.AppKit              	0x997ad28c -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 119
    11  com.apple.AppKit              	0x997a36dc -[NSApplication run] + 855
    12  com.apple.AppKit              	0x997468e6 NSApplicationMain + 1053
    13  com.yoyogames.macyoyorunner   	0x00003123 main + 165
    14  com.yoyogames.macyoyorunner   	0x00003075 start + 53
    
    Thread 1:
    0   libsystem_kernel.dylib        	0x9a26c0ee __workq_kernreturn + 10
    1   libsystem_c.dylib             	0x9480204c _pthread_workq_return + 45
    2   libsystem_c.dylib             	0x94801e19 _pthread_wqthread + 448
    3   libsystem_c.dylib             	0x947e9cca start_wqthread + 30
    
    Thread 2:: Dispatch queue: com.apple.libdispatch-manager
    0   libsystem_kernel.dylib        	0x9a26c9ae kevent + 10
    1   libdispatch.dylib             	0x92ec1cc5 _dispatch_mgr_invoke + 993
    2   libdispatch.dylib             	0x92ec17fd _dispatch_mgr_thread + 53
    
    Thread 3 Crashed:: Dispatch queue: com.apple.root.default-priority
    0   libGL.dylib                   	0x92919a66 glViewport + 13
    1   com.yoyogames.macyoyorunner   	0x000c86f9 -[YYGLView beginRender:] + 229
    2   com.yoyogames.macyoyorunner   	0x00004d57 -[Mac_RunnerAppDelegate performGameStep] + 97
    3   com.yoyogames.macyoyorunner   	0x00005919 -[Mac_RunnerAppDelegate doGameEngine] + 96
    4   com.apple.CoreFoundation      	0x941833ed __invoking___ + 29
    5   com.apple.CoreFoundation      	0x94183327 -[NSInvocation invoke] + 279
    6   com.apple.Foundation          	0x913f287d -[NSInvocationOperation main] + 81
    7   com.apple.Foundation          	0x913ea0f9 -[__NSOperationInternal start] + 740
    8   com.apple.Foundation          	0x913e9e0e -[NSOperation start] + 67
    9   com.apple.Foundation          	0x913f1f09 __block_global_6 + 135
    10  libdispatch.dylib             	0x92ec2fe3 _dispatch_call_block_and_release + 15
    11  libdispatch.dylib             	0x92ebed0a _dispatch_client_callout + 46
    12  libdispatch.dylib             	0x92ebff6a _dispatch_worker_thread2 + 285
    13  libsystem_c.dylib             	0x94801e12 _pthread_wqthread + 441
    14  libsystem_c.dylib             	0x947e9cca start_wqthread + 30
    
    Thread 4:
    0   libsystem_kernel.dylib        	0x9a26c0ee __workq_kernreturn + 10
    1   libsystem_c.dylib             	0x9480204c _pthread_workq_return + 45
    2   libsystem_c.dylib             	0x94801e19 _pthread_wqthread + 448
    3   libsystem_c.dylib             	0x947e9cca start_wqthread + 30
    
    Thread 5:
    0   libsystem_kernel.dylib        	0x9a26c0ee __workq_kernreturn + 10
    1   libsystem_c.dylib             	0x9480204c _pthread_workq_return + 45
    2   libsystem_c.dylib             	0x94801e19 _pthread_wqthread + 448
    3   libsystem_c.dylib             	0x947e9cca start_wqthread + 30
    
    Thread 3 crashed with X86 Thread State (32-bit):
      eax: 0x00000000  ebx: 0x001a2980  ecx: 0x000003c6  edx: 0x00000000
      edi: 0x001a2984  esi: 0x01d8d520  ebp: 0xb0183eb8  esp: 0xb0183ea0
       ss: 0x00000023  efl: 0x00010286  eip: 0x92919a66   cs: 0x0000001b
       ds: 0x00000023   es: 0x00000023   fs: 0x00000023   gs: 0x0000000f
      cr2: 0x00000000
    Logical CPU: 0
    Thanks
     
  2. macrumors 68000

    cal6n

    Joined:
    Jul 25, 2004
    Location:
    Brighton, UK
    #2
    Is there any reason you haven't updates to 10.8.3? There have been a lot of bugs squashed since 10.8.0 was released.
     
  3. macrumors 6502a

    Joined:
    Mar 19, 2008
    Location:
    North Shore, MA
    #3
    Have you actually read through the crash log? More often than not, a single thread is marked as having crashed the app; This marker is right next to the thread's name. Just look through the backtrace of the Crashed thread and see where in your code you should start looking for issues. Also an EXC_BAD_ACCESS exception at address 0x0000000000000000 exception usually indicates a NULL pointer access.
     
  4. thread starter macrumors newbie

    Joined:
    Apr 11, 2013
    #4
    I'm downloading the 10.8.3 update now and will try again.

    I'm using a game framework called GameMaker Studio. In the log I posted it says thread 3 crashed but I don't know where I would need to look in my code and don't know what a NULL pointer access is. I'm running Mountain Lion via VMware on a Windows 7 machine if that's any help.
     
  5. macrumors 6502a

    Joined:
    Mar 19, 2008
    Location:
    North Shore, MA
    #5
    That is extremely important information! I'm not sure how compatible Mac OS X is with VMWare's emulated graphics chipset so that could be your problem since it looks like the app is crashing when it drops into the OpenGL layer. Unfortunately, without a physical Mac to test it on it will be difficult to narrow the issue down any further; if you are planning on releasing and supporting the app I would strongly advise either getting a cheap mac (a year or two old Mac Mini should work fine, assuming your game isn't too graphically intensive) or finding a friend with one.
     
  6. thread starter macrumors newbie

    Joined:
    Apr 11, 2013
    #6
    Okay I just tested it on my friend's iMac and it works fine there. My computer must not be able to handle a virtual iMac machine or something. Shame. Thanks for your help guys.
     

Share This Page