Important: Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct
QtCreator crashes on me, at least 4 or 5 times a day. Is anyone else having this problem?
There's no discernible pattern to the crash; it sometimes happens when it's just sitting there & I'm staring at my code.
My system is a Mac 10.9.4, using Qt 5.3.1 and QtCreator 3.2.1 (although the same crash happened has happened under 3.1.2). I've clean-installed Qt a couple times (when upgrading) and still have the crashes.
Here's the top of a typical crash log (I can send more if that's helpful):
Process: Qt Creator 
Path: /Users/USER/*/Qt Creator.app/Contents/MacOS/Qt Creator
Version: 3.2.1 (3.2.1)
Code Type: X86-64 (Native)
Parent Process: launchd 
Responsible: Qt Creator 
User ID: 501
Date/Time: 2014-09-02 11:44:49.877 -0700
OS Version: Mac OS X 10.9.4 (13E28)
Report Version: 11
Anonymous UUID: 50ED43B9-7091-C91C-39F7-B4C19088247F
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000004
VM Regions Near 0x4:
__TEXT 00000001068a4000-00000001068b9000 [ 84K] r-x/rwx SM=COW /Users/USER/*/Qt Creator.app/Contents/MacOS/Qt Creator
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 QtCore 0x0000000107784a3d QCoreApplication::notifyInternal(QObject*, QEvent*) + 93
1 QtCore 0x00000001077db256 QTimerInfoList::activateTimers() + 1302
2 libqcocoa.dylib 0x0000000109689445 0x10966b000 + 123973
3 com.apple.CoreFoundation 0x00007fff934db5b1 CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION + 17
4 com.apple.CoreFoundation 0x00007fff934ccc62 __CFRunLoopDoSources0 + 242
5 com.apple.CoreFoundation 0x00007fff934cc3ef __CFRunLoopRun + 831
6 com.apple.CoreFoundation 0x00007fff934cbe75 CFRunLoopRunSpecific + 309
7 com.apple.HIToolbox 0x00007fff8fbcea0d RunCurrentEventLoopInMode + 226
8 com.apple.HIToolbox 0x00007fff8fbce7b7 ReceiveNextEventCommon + 479
9 com.apple.HIToolbox 0x00007fff8fbce5bc _BlockUntilNextEventMatchingListInModeWithFilter + 65
10 com.apple.AppKit 0x00007fff911f424e _DPSNextEvent + 1434
11 com.apple.AppKit 0x00007fff911f389b -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 122
12 com.apple.AppKit 0x00007fff911e799c -[NSApplication run] + 553
13 libqcocoa.dylib 0x000000010968a1d4 0x10966b000 + 127444
14 QtCore 0x0000000107781acd QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) + 381
15 QtCore 0x0000000107785007 QCoreApplication::exec() + 359
16 org.qt-project.qtcreator 0x00000001068b1bc5 main + 23573
17 org.qt-project.qtcreator 0x00000001068a8d44 start + 52
Sometimes the the "Exception codes" line looks like this:
Exception Codes: EXC_I386_GPFLT
Any advice appreciated!
Hi and welcome to devnet,
When you built Qt Creator, was it with a self-built Qt ?
I downloaded the binary of Qt Creator, rather than building from source.
I've submitted a bug report, QTCREATORBUG-12964
Ok, good, thanks for sharing the link
hskoglund last edited by
Hi, I see in your crash log QTimerInfoList::activateTimers(), and there are many bug reports filed for that function, like "this one":https://bugreports.qt-project.org/browse/QTCREATORBUG-11262
But the good news is, now there seems to be a solution, perhaps it's applicable for you also: launch QtCreator and select About Plugins... and check if you have the UpdateInfo plugin enabled. If so disable it. (This is from the bug report link above).
Thanks, hskoglund! The UpdateInfo plugin was enabled, so I've disabled it and restarted.
So far, no crashes! I will report back again after I have had a few more hours of use.
Yep, that definitely fixed it! No crashes since turning off the UpdateInfo plugin.
Thanks everyone! :-D