Version-Release number of selected component: qt-creator-3.0.1-2.fc19 Additional info: reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: /usr/bin/qtcreator crash_function: deref executable: /usr/bin/qtcreator kernel: 3.13.9-100.fc19.x86_64 runlevel: N 5 type: CCpp uid: 1000 var_log_messages: Apr 23 12:51:09 OZDT0004 abrt-hook-ccpp[6759]: Saved core dump of pid 1909 (/usr/bin/qtcreator) to /var/tmp/abrt/ccpp-2014-04-23-12:50:54-1909 (501297152 bytes) Truncated backtrace: Thread no. 1 (10 frames) #0 deref at /usr/include/QtCore/qatomic_x86_64.h:133 #1 ~QString at /usr/include/QtCore/qstring.h:880 #2 node_destruct at /usr/include/QtCore/qlist.h:433 #3 free at /usr/include/QtCore/qlist.h:757 #4 QList<QString>::~QList at /usr/include/QtCore/qlist.h:732 #5 ~QStringList at /usr/include/QtCore/qstringlist.h:66 #6 Todo::Internal::CppTodoItemsScanner::shouldProcessFile at cpptodoitemsscanner.cpp:53 #7 Todo::Internal::CppTodoItemsScanner::documentUpdated at cpptodoitemsscanner.cpp:75 #8 Todo::Internal::CppTodoItemsScanner::qt_static_metacall at .moc/release-shared/moc_cpptodoitemsscanner.cpp:49 #9 QMetaObject::activate at kernel/qobject.cpp:3547
Created attachment 888849 [details] File: backtrace
Created attachment 888850 [details] File: cgroup
Created attachment 888851 [details] File: core_backtrace
Created attachment 888852 [details] File: dso_list
Created attachment 888853 [details] File: environ
Created attachment 888854 [details] File: exploitable
Created attachment 888855 [details] File: limits
Created attachment 888856 [details] File: maps
Created attachment 888857 [details] File: open_fds
Created attachment 888858 [details] File: proc_pid_status
Thanks for the bug report. Can you remember what you were doing when the crash occurred? Is it reproducible?
Closing since no reply in one month. Please reopen if you can reproduce the issue and provide more information. Thanks.
Hmm, I thought I answered this one by mail... Maybe forgot to press Send... This issue occurs when Creator has been running for a couple of days. I've been unable to reproduce it with the current version however, so it might be fixed. If it occurs again, I'll issue another bug.