Every so often choqok will crash, apparently while it is fetching new Tweets from Twitter. It is neither consistent nor repeatable; restarting choqok immediately after the crash won't necessarily make it crash again. I have captured a number of stack backtraces and they seem to all be running through the same code path. I'm running the latest git version in a hand-built RPM on Fedora 18. I would be happy to run patches or try other diagnosis steps. As I've captured a number of stack backtraces (with full symbols) I'll attach one of them here. Reproducible: Sometimes Stack backtrace from the 'developers' tab of the automatic crash reporting stuff: Application: Choqok (choqok), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash Handler] #5 QDate::isValid (this=0x10000000104) at tools/qdatetime.cpp:330 #6 0x0000003eed489910 in QDateTime::isValid (this=0xb889da8) at tools/qdatetime.cpp:2225 #7 0x00000031af64f379 in Choqok::UI::PostWidget::formatDateTime (this=0x975a8b0, time=...) at /usr/src/debug/choqok-1.3/libchoqok/ui/postwidget.cpp:454 #8 0x00000031af64ec47 in Choqok::UI::PostWidget::updateUi (this=0x975a8b0) at /usr/src/debug/choqok-1.3/libchoqok/ui/postwidget.cpp:246 #9 0x0000003eed58cd6f in QMetaObject::activate (sender=0x7cc36f0, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3539 #10 0x0000003eed58c07c in QObject::event (this=0x7cc36f0, e=<optimized out>) at kernel/qobject.cpp:1156 #11 0x00000030dc3ca5cc in QApplicationPrivate::notify_helper (this=this@entry=0x82e870, receiver=receiver@entry=0x7cc36f0, e=e@entry=0x7fff7a36ae70) at kernel/qapplication.cpp:4562 #12 0x00000030dc3cea4a in QApplication::notify (this=0x7fff7a36b220, receiver=0x7cc36f0, e=0x7fff7a36ae70) at kernel/qapplication.cpp:4423 #13 0x00000034d2246f16 in KApplication::notify(QObject*, QEvent*) () from /lib64/libkdeui.so.5 #14 0x0000003eed57793e in QCoreApplication::notifyInternal (this=0x7fff7a36b220, receiver=0x7cc36f0, event=0x7fff7a36ae70) at kernel/qcoreapplication.cpp:949 #15 0x0000003eed5a87f2 in sendEvent (event=0x7fff7a36ae70, receiver=<optimized out>) at kernel/qcoreapplication.h:231 #16 QTimerInfoList::activateTimers (this=0x82fd60) at kernel/qeventdispatcher_unix.cpp:622 #17 0x0000003eed5a5914 in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:186 #18 timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:180 #19 0x0000003eed5a5931 in idleTimerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:233 #20 0x0000003ee2847a55 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #21 0x0000003ee2847d88 in g_main_context_iterate.isra.24 () from /lib64/libglib-2.0.so.0 #22 0x0000003ee2847e44 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #23 0x0000003eed5a5f86 in QEventDispatcherGlib::processEvents (this=0x7b8120, flags=...) at kernel/qeventdispatcher_glib.cpp:424 #24 0x00000030dc46a73e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:207 #25 0x0000003eed5765ef in QEventLoop::processEvents (this=this@entry=0x7fff7a36b0f0, flags=...) at kernel/qeventloop.cpp:149 #26 0x0000003eed576878 in QEventLoop::exec (this=0x7fff7a36b0f0, flags=...) at kernel/qeventloop.cpp:204 #27 0x0000003eed57b708 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1221 #28 0x0000000000409946 in main (argc=1, argv=0x7fff7a36b368) at /usr/src/debug/choqok-1.3/choqok/main.cpp:63
*** This bug has been marked as a duplicate of bug 321307 ***