Mac Version, instant crash on luanch right after buying on Steam

Home Forums Support Mac Version, instant crash on luanch right after buying on Steam

Tagged: , ,

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
  • #13703

    Hello, i have just bought the Mac version via Steam, and the app is completely unusable, it crashes on launch right away.

    This is really frustrating.

    I see the main menu screen coming, i hear the music playing, but the game’s mouse pointer is stuck at the top left corner of the screen, and if i move my mouse all i see is a beach ball.
    After about 5 seconds, the game crashes.

    I am running Mac OS X 10.10.2, below are the computer specs and the crash dump. Somehow it seems to be looking for a method of NSTouch that is not there anymore…

    These are my computer specs:

    Model Name: MacBook Pro
    Model Identifier: MacBookPro11,3
    Processor Name: Intel Core i7
    Processor Speed: 2.3 GHz
    Number of Processors: 1
    Total Number of Cores: 4
    L2 Cache (per Core): 256 KB
    L3 Cache: 6 MB
    Memory: 16 GB
    Boot ROM Version: MBP112.0138.B11
    SMC Version (system): 2.19f9


    Chipset Model: NVIDIA GeForce GT 750M
    Type: GPU
    Bus: PCIe
    PCIe Lane Width: x8
    VRAM (Total): 2048 MB
    Vendor: NVIDIA (0x10de)
    Device ID: 0x0fe9
    Revision ID: 0x00a2
    ROM Revision: 3776
    gMux Version: 4.0.8 [3.2.8]

    Crash Dump:

    11/22/14 6:09:49.043 PM TrainFever[1365]: *** Terminating app due to uncaught exception ‘NSInvalidArgumentException’, reason: ‘-[NSTouch _initWithPreviousTouch:newPhase:position:isResting:]: unrecognized selector sent to instance 0x7fcaf9c73750’
    *** First throw call stack:
    0 CoreFoundation 0x00007fff899e366c __exceptionPreprocess + 172
    1 libobjc.A.dylib 0x00007fff903fc76e objc_exception_throw + 43
    2 CoreFoundation 0x00007fff899e66dd -[NSObject(NSObject) doesNotRecognizeSelector:] + 205
    3 CoreFoundation 0x00007fff8992daa4 ___forwarding___ + 1028
    4 CoreFoundation 0x00007fff8992d618 _CF_forwarding_prep_0 + 120
    5 AppKit 0x00007fff8e1f341c -[NSEvent _initTouches] + 2048
    6 AppKit 0x00007fff8e19c26d -[NSEvent _initWithCGSEvent:eventRef:] + 3253
    7 AppKit 0x00007fff8e036584 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 422
    8 libSDL2-2.0.0.dylib 0x000000010c801ad9 Cocoa_PumpEvents + 217
    9 libSDL2-2.0.0.dylib 0x000000010c79b28d SDL_PollEvent_REAL + 29
    10 TrainFever 0x000000010c004cec TrainFever + 5061868
    11 TrainFever 0x000000010c004c21 TrainFever + 5061665
    12 TrainFever 0x000000010bb33806 TrainFever + 10246
    13 TrainFever 0x000000010bee8759 TrainFever + 3897177
    14 TrainFever 0x000000010bb32444 TrainFever + 5188
    15 ??? 0x0000000000000001 0x0 + 1


    Ok, i did some research, im a mac dev myself, problem seems to be with the 10.10.2 update removing certain methods from the NSTouch class…..

    The app works if i dont touch the touchpad, as soon as i touch the touchpad, it crashes.

    Other apps like Chromium are having the exact same issue im having

    When can we expect a fix for this ?

    // Diego

    • This reply was modified 7 years ago by DiegoMax.

    And some more debug, the problem is specifically with isResting, which is deprecated in 10.10, and clearly removed from 10.10.2

    I guess i will have to wait for an update.


    // Diego



    Thank you for the research.

    Since 10.10.2 is a beta and since the deprecated function is called from libSDL, we’ll wait for the libSDL developers (or Apple) to fix this.

    We’re keeping track about the changes.

    • This reply was modified 7 years ago by mikael.

    Sure thing, im aware its beta, but i thought you would be interested to know before it goes public.


    // Diego

Viewing 5 posts - 1 through 5 (of 5 total)
  • The forum ‘Support’ is closed to new topics and replies.