[Development] crash when activating timers
Ziller Eike
Eike.Ziller at digia.com
Wed Aug 13 16:32:13 CEST 2014
For Qt Creator we get the following crash reported:
https://bugreports.qt-project.org/browse/QTCREATORBUG-11262
It seems to happen randomly, on unix (i.e. OS X and Linux) but possibly not on Windows, at least Qt 5.2.1 and later, and the seemingly only person in the Berlin office which also gets this crash once in a while, can only reproduce it with the binary package that we provide on downloads.qt-project.org.
The backtrace doesn’t give much insight either, except that it happens when activating timers:
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff6536545 in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /home/usuario/Qt/Tools/QtCreator/bin/../lib/qtcreator/libQt5Core.so.5
(gdb) bt
#0 0x00007ffff6536545 in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /home/usuario/Qt/Tools/QtCreator/bin/../lib/qtcreator/libQt5Core.so.5
#1 0x00007ffff6585fdc in QTimerInfoList::activateTimers() () from /home/usuario/Qt/Tools/QtCreator/bin/../lib/qtcreator/libQt5Core.so.5
#2 0x00007ffff65867ed in ?? () from /home/usuario/Qt/Tools/QtCreator/bin/../lib/qtcreator/libQt5Core.so.5
#3 0x00007ffff52a93b6 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4 0x00007ffff52a9708 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5 0x00007ffff52a97ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6 0x00007ffff6586fc4 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /home/usuario/Qt/Tools/QtCreator/bin/../lib/qtcreator/libQt5Core.so.5
#7 0x00007ffff65352cb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /home/usuario/Qt/Tools/QtCreator/bin/../lib/qtcreator/libQt5Core.so.5
#8 0x00007ffff653933e in QCoreApplication::exec() () from /home/usuario/Qt/Tools/QtCreator/bin/../lib/qtcreator/libQt5Core.so.5
#9 0x000000000040a561 in ?? ()
#10 0x00007ffff57d4de5 in __libc_start_main (main=0x4068f0, argc=1, ubp_av=0x7fffffffdf78, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffffffdf68)
at libc-start.c:260
#11 0x000000000040aa01 in ?? ()
#12 0x00007fffffffdf68 in ?? ()
#13 0x000000000000001c in ?? ()
#14 0x0000000000000001 in ?? ()
#15 0x00007fffffffe2e9 in ?? ()
#16 0x0000000000000000 in ?? ()
(gdb)
So my question: Does anyone have any idea how this could possibly happen, how we could reproduce and/or debug and fix it?
Br, Eike
--
Eike Ziller, Senior Software Engineer - Digia, Qt
Digia Germany GmbH, Rudower Chaussee 13, D-12489 Berlin
Geschäftsführer: Mika Pälsi, Juha Varelius, Tuula Haataja
Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B
More information about the Development
mailing list