[Mac] It Crashes when it's about to get to the game.

[rayzapark]

I bought this game on the app store several days ago. And the first time I ran this game, it was perfectly played.

But now, it crashes right after the loading or the motion picture. I don't know why.

here is the report can anybody tell me what is wrong here thx.

Crashed Thread:  1  Dispatch queue: com.apple.libdispatch-managerException Type:  EXC_CRASH (SIGBUS)Exception Codes: 0x0000000000000000, 0x0000000000000000Thread 1 Crashed:: Dispatch queue: com.apple.libdispatch-manager0   libsystem_kernel.dylib        	0x9137d90a kevent + 101   libdispatch.dylib             	0x97526e04 _dispatch_mgr_invoke + 9692   libdispatch.dylib             	0x97525853 _dispatch_mgr_thread + 53Thread 1 crashed with X86 Thread State (32-bit):  eax: 0x00000004  ebx: 0xacd84c00  ecx: 0xb00805dc  edx: 0x9137d90a  edi: 0xb0080720  esi: 0x97526a4c  ebp: 0xb0080738  esp: 0xb00805dc   ss: 0x00000023  efl: 0x00000247  eip: 0x9137d90a   cs: 0x0000000b   ds: 0x00000023   es: 0x00000023   fs: 0x00000023   gs: 0x0000000f  cr2: 0x0e628000Logical CPU: 0

[ibanez81]

I'm getting a similar crash on my 27-inch iMac:(Mid 2011, 3.1 GHz Intel Core i5, 8GB RAM, AMD Radeon HD 6970M 1024 MB, OS X 10.7.5):Thread 1 Crashed ↩:: Dispatch queue: com.apple.libdispatch-manager0 libsystem_kernel.dylib 0x9997190a kevent + 101 libdispatch.dylib 0x9c7a5e04 _dispatch_mgr_invoke + 9692 libdispatch.dylib 0x9c7a4853 _dispatch_mgr_thread + 53I tried a few things to test: - Restarting iMac - Playing in "windowed-mode" - Lowering the game resolution - Deleting and reinstalling from the MASSame issue

[keith]

Exactly the same thing happening to me, just bought today from the app store and Soon as it tries to launch the game after opening scene it crashes to desktop.

2011 imac

2.5 Ghz intel core i5

4Gig ram

is any thing being done about this?

[Corey]

I bought this game on the app store several days ago. And the first time I ran this game, it was perfectly played. But now, it crashes right after the loading or the motion picture. I don't know why.

Hey, thanks for including all those details. We're trying to track down why this error occurs. It's very interesting that it use to work, but now no longer does.So here's a few questions for you...1) Do you know if anything changed on your system since it first worked? (Updated OSX, new software, added new hardware?)2) Do you have ANYTHING else running. (A web browser, chat programs, or background software). To check background software, look at the top right where your clock is on OSX. Are there any icons showing apps running there? Try closing them if you can.3) Can you paste the part of your call stack that has:OSX version #Hardware / System build info.Thanks!