User Avatar Image

OS X 10.9 Instant Crash [Fixed in update]

posted by wernerdev on - last edited by DjNDB - Viewed by 40K users

I am running OS X 10.9 GM, but The Walking Dead instantly crashes when trying to start it.
It seems it has to do with the Code Signature of the game: Exception Type: EXC_CRASH (Code Signature Invalid)

Is this known? Working in a fix? Because 10.9 is going live somewhere near the end of this month...

  • Any fix for this???

  • I have the same problem.
    Support service to spit?

  • Today I got this very helpful reply from Support:

    I apologize for the delayed response. Due to MAC OS 10.9 not being available before the The Walking Dead was released in its entirety, we recommend playing on 10.8.x and below.

    I told them that going back to 10.8 was no solution since 10.9 is about to be released by the end of this month. They need to fix this!

    I love their games, but the support is very bad...

  • I surely hope they fix this, I just bought the game and I'm not able to play it. I don't think about going back to OSX 10.8. If their statement is that the game won't be updated since TWD came out earlier than 10.9 than I'm going to request a refund.

    Please fix this issue!

  • Since OS X 10.9 officially released yesterday I think it's about time for a fix! Please help your customers, or else this will be the last TellTaleGames game I bought...

  • User Avatar Image
    DjNDB Moderator

    I wonder if it's really just a code signing issue or more.

    Does the game work if you set gatekeeper to "Anywhere" in "System Preferences/Security & Privacy"?

    If that doesn't work, how about if you disable the "assessment subsystem"?
    Make sure to reenable it after the test and set gatekeeper back to the setting you prefer.

    sudo spctl --master-disable

    sudo spctl --master-enable

    • Hey there DjNDB,

      Still having the Exception Type: EXC_CRASH (Code Signature Invalid) with gatekeeper on anywhere and/or with spctl --master-disable.
      I wonder if the steam version has the same problem?

  • The trace from the crash is as follows:
    Process: WalkingDead101 [1194]
    Path: /Applications/
    Identifier: com.telltalegames.WalkingDead101
    Version: ???
    Code Type: X86 (Native)
    Parent Process: launchd [223]
    Responsible: WalkingDead101 [1194]
    User ID: 502

    Date/Time: 2013-10-24 02:10:52.097 -0500
    OS Version: Mac OS X 10.9 (13A603)
    Report Version: 11
    Anonymous UUID: 8D75DF2D-DACD-A863-DE14-B89654C8042D

    Crashed Thread: 0

    Exception Type: EXC_CRASH (Code Signature Invalid)
    Exception Codes: 0x0000000000000000, 0x0000000000000000

    VM Regions Near 0 (cr2):
    --> VM_ALLOCATE 0000000000000000-0000000000001000 [ 4K] ---/--- SM=NUL
    mapped file 0000000000001000-000000000056b000 [ 5544K] r-x/rwx SM=COW /Applications/

    Thread 0 Crashed:
    0 dyld 0x8fe2e030 _dyld_start + 0

    Thread 0 crashed with X86 Thread State (32-bit):
    eax: 0x00000000 ebx: 0x00000000 ecx: 0x00000000 edx: 0x00000000
    edi: 0x00000000 esi: 0x00000000 ebp: 0x00000000 esp: 0xbffffd8c
    ss: 0x00000023 efl: 0x00000200 eip: 0x8fe2e030 cs: 0x0000001b
    ds: 0x00000023 es: 0x00000023 fs: 0x00000000 gs: 0x00000000
    cr2: 0x00000000

    Logical CPU: 0
    Error Code: 0x00000000
    Trap Number: 0

    Binary Images:
    0x8fe2d000 - 0x8fe5f417 dyld (???) <4B280BB1-55F8-313F-86A6-8ADD644ED69E> /usr/lib/dyld

    External Modification Summary:
    Calls made by other processes targeting this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
    Calls made by this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
    Calls made by all processes on this machine:
    task_for_pid: 721
    thread_create: 0
    thread_set_state: 0

    VM Region Summary:
    ReadOnly portion of Libraries: Total=280K resident=280K(100%) swapped_out_or_unallocated=0K(0%)
    Writable regions: Total=8508K written=0K(0%) resident=12K(0%) swapped_out=0K(0%) unallocated=8496K(100%)

    =========== =======
    Stack 64.0M
    VM_ALLOCATE (reserved) 148K reserved VM address space (unallocated)
    __DATA 168K
    __LINKEDIT 76K
    __TEXT 204K
    mapped file 274.6M
    shared memory 4K
    =========== =======
    TOTAL 339.2M
    TOTAL, minus reserved VM space 339.0M

    Model: iMac12,2, BootROM IM121.0047.B1F, 4 processors, Intel Core i5, 2.7 GHz, 4 GB, SMC 1.72f1
    Graphics: AMD Radeon HD 6770M, AMD Radeon HD 6770M, PCIe, 512 MB
    Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1333 MHz, 0x80CE, 0x4D34373142353637334648302D4348392020
    Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1333 MHz, 0x80CE, 0x4D34373142353637334648302D4348392020
    AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x9A), Atheros 9380:
    Bluetooth: Version 4.2.0f6 12982, 3 services, 23 devices, 1 incoming serial ports
    Network Service: AirPort, AirPort, en1
    Serial ATA Device: ST31000528AS, 1 TB
    Serial ATA Device: OPTIARC DVD RW AD-5680H, 4.19 GB
    USB Device: Hub
    USB Device: USB Optical Mouse
    USB Device: IR Receiver
    USB Device: Internal Memory Card Reader
    USB Device: FaceTime HD Camera (Built-in)
    USB Device: Hub
    USB Device: BRCM2046 Hub
    USB Device: Bluetooth USB Host Controller
    Thunderbolt Bus: iMac, Apple Inc., 22.1

    • The error in the crash is EXC_CRASH (Code Signature Invalid) - sounds like it could be fixed by re-issuing the binary with a new signature.

  • Wow this is really really bad. Not a single word of support yet... I am also starting to think about getting a refund.
    And the responses to tickets are making me cry. Basically they are saying: It's not working on 10.9, deal with it.

    It's a shame!

  • I have emailed support and have not gotten a response in over a week... I am very disappointed in this not being updated to work properly.

  • It won't be of much help, but I bought today the Steam version, and it runs fine on my MacBook Pro (late 2011) with 10.9.0 installed. I've not played much though, but so far no crash. It should not be too difficult for Telltale Games to release a fixed version, so.

This discussion has been closed.