Problems with Open-Source Downloads read and

The Latest QT SDK/Creator crashes on startup on (QT 5.2.0 on OSX Mavericks 10.9.1)

  • Hi,

    I'm unable to run QT Creator from the latest 5.2.0 SDK on OSX Mavericks.

    Here is the first couple of lines from the logs:

    Process: Qt Creator [666]
    Path: /Users/USER/*/Qt Creator
    Identifier: org.qt-project.qtcreator
    Version: 3.0.0 (3.0.0)
    Code Type: X86-64 (Native)
    Parent Process: launchd [256]
    Responsible: Qt Creator [666]
    User ID: 501

    Date/Time: 2014-01-01 20:45:02.660 -0800
    OS Version: Mac OS X 10.9.1 (13B42)
    Report Version: 11
    Anonymous UUID: 5DE701FC-4D46-6FE9-2494-5146C17BC4E5

    Crashed Thread: 0 Dispatch queue:

    Exception Type: EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: KERN_INVALID_ADDRESS at 0x000000000000016f

    Where can I send the full crash report to help the developers out ??

    Any help would be appreciated..



  • Hi Mike,
    i have also maverick (on my mac mini) and 5.2.0 sdk qtcreator runs without problems.


  • I also installed on my MacBook Air and it works on that machine but it does not work on my Mac Pro...

    I'm still experiencing this crash on my Mac Pro.... Seems to crash when you go to the "New Project" dialog...

    so I'm not quite sure what is different between the setup of the two machines..

    Both machines are running Mavericks 1.9.1.

    I can code on the MacBook Air ok... but I'd still like to be able to run on the Mac Pro which is my primary workstation...

    Any ideas or help would be appreciated...


  • I have the exact same problem. I have Qt Creator 3.0.1 on 10.9.2 working perfectly on my MacBook Pro, but crashing miserably on a Mac Pro whenever I go near the path field in a new project. I have tried building it from source myself, with the same results.

  • Lifetime Qt Champion


    You should have a look at the "bug report system": to see whether it's something known. If not please consider opening a new bug report with as much detail possible regarding the different Macs where it's working and not (OS exact version, graphic card vendor + driver version etc…)

Log in to reply