Bug 348005 - Kmail crashes
Summary: Kmail crashes
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2015-05-20 12:44 UTC by Carl-Erwin Griffith
Modified: 2018-01-31 16:50 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Carl-Erwin Griffith 2015-05-20 12:44:42 UTC
Application: kmail (4.14.8)
KDE Platform Version: 4.14.8
Qt Version: 4.8.6
Operating System: Linux 3.19.4-1-desktop x86_64
Distribution: "openSUSE 20150516 (Tumbleweed) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:

using kdevelop + konsole + chromium normally

- Unusual behavior I noticed:

krunner crashes
plasmashell lockups (menu)

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
81	T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7fe9ba9568c0 (LWP 635))]

Thread 4 (Thread 0x7fe9945bb700 (LWP 638)):
#0  0x00007fe9b07cf91f in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007fe9acba5896 in WTF::TCMalloc_PageHeap::scavengerThread() () at /usr/lib64/libQtWebKit.so.4
#2  0x00007fe9acba58c9 in  () at /usr/lib64/libQtWebKit.so.4
#3  0x00007fe9b07cb484 in start_thread (arg=0x7fe9945bb700) at pthread_create.c:333
#4  0x00007fe9b7c7aa4d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7fe953418700 (LWP 639)):
#0  0x00007fe9b07cf91f in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007fe9ac9183cd in JSC::BlockAllocator::blockFreeingThreadMain() () at /usr/lib64/libQtWebKit.so.4
#2  0x00007fe9acbcd406 in WTF::wtfThreadEntryPoint(void*) () at /usr/lib64/libQtWebKit.so.4
#3  0x00007fe9b07cb484 in start_thread (arg=0x7fe953418700) at pthread_create.c:333
#4  0x00007fe9b7c7aa4d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7fe9525aa700 (LWP 640)):
[KCrash Handler]
#5  0x00007fe9a6f03b3e in _dbus_counter_notify (counter=0x2542a10) at dbus-resources.c:187
#6  0x00007fe9a6efcbc2 in free_counter (element=0x2542a10, data=0x3d1cd40) at dbus-message.c:639
#7  0x00007fe9a6efd0d2 in dbus_message_unref (message=0x3d1cd40) at dbus-message.c:661
#8  0x00007fe9a6efd0d2 in dbus_message_unref (message=0x3d1cd40) at dbus-message.c:1707
#9  0x00007fe9b2383b09 in QDBusArgument::~QDBusArgument() (message=<optimized out>) at qdbus_symbols_p.h:296
#10 0x00007fe9b2383b09 in QDBusArgument::~QDBusArgument() (this=<optimized out>, __in_chrg=<optimized out>) at qdbusargument.cpp:66
#11 0x00007fe9b2383b09 in QDBusArgument::~QDBusArgument() (this=0x2542a10, __in_chrg=<optimized out>) at qdbusargument.cpp:348
#12 0x00007fe9b236076e in qMetaTypeDeleteHelper<QDBusArgument>(QDBusArgument*) (t=0x365eb10) at ../../src/corelib/kernel/qmetatype.h:134
#13 0x00007fe9b92bb9b3 in clear(QVariant::Private*) (d=0x3975ff0) at kernel/qvariant.cpp:290
#14 0x00007fe9b234fa5c in QList<QVariant>::~QList() (this=<optimized out>, to=<optimized out>, from=<optimized out>) at ../../src/corelib/tools/qlist.h:431
#15 0x00007fe9b234fa5c in QList<QVariant>::~QList() (this=<optimized out>, data=<optimized out>) at ../../src/corelib/tools/qlist.h:757
#16 0x00007fe9b234fa5c in QList<QVariant>::~QList() (this=0x2542a10, __in_chrg=<optimized out>) at ../../src/corelib/tools/qlist.h:732
#17 0x00007fe9b2363f7f in QDBusMessage::~QDBusMessage() (this=0x2542a10, __in_chrg=<optimized out>) at qdbusmessage.cpp:537
#18 0x00007fe9b2360d56 in QDBusCallDeliveryEvent::~QDBusCallDeliveryEvent() (this=0x38264c0, __in_chrg=<optimized out>) at qdbusintegrator_p.h:93
#19 0x00007fe9b2360d56 in QDBusCallDeliveryEvent::~QDBusCallDeliveryEvent() (this=0x38264c0, __in_chrg=<optimized out>) at qdbusintegrator_p.h:93
#20 0x00007fe9b929b596 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x29df940) at kernel/qcoreapplication.cpp:1593
#21 0x00007fe9b929ba33 in QCoreApplication::sendPostedEvents(QObject*, int) (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1470
#22 0x00007fe9b92c590e in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) () at kernel/qcoreapplication.h:236
#23 0x00007fe9b92c590e in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) (s=0x7fe9440012e0) at kernel/qeventdispatcher_glib.cpp:300
#24 0x00007fe9af9aac74 in g_main_context_dispatch (context=0x7fe9440009a0) at gmain.c:3122
#25 0x00007fe9af9aac74 in g_main_context_dispatch (context=context@entry=0x7fe9440009a0) at gmain.c:3737
#26 0x00007fe9af9aaec8 in g_main_context_iterate (context=context@entry=0x7fe9440009a0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3808
#27 0x00007fe9af9aaf6c in g_main_context_iteration (context=0x7fe9440009a0, may_block=1) at gmain.c:3869
#28 0x00007fe9b92c50ce in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x7fe9440008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:450
#29 0x00007fe9b9296e7f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7fe9525a9d20, flags=...) at kernel/qeventloop.cpp:149
#30 0x00007fe9b9297175 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7fe9525a9d20, flags=...) at kernel/qeventloop.cpp:204
#31 0x00007fe9b919451f in QThread::exec() (this=<optimized out>) at thread/qthread.cpp:538
#32 0x00007fe9b9196bff in QThreadPrivate::start(void*) (arg=0x25f1dc0) at thread/qthread_unix.cpp:349
#33 0x00007fe9b07cb484 in start_thread (arg=0x7fe9525aa700) at pthread_create.c:333
#34 0x00007fe9b7c7aa4d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fe9ba9568c0 (LWP 635)):
#0  0x00007fe9b7c6e59d in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fe9af9ebb20 in g_wakeup_acknowledge (__nbytes=16, __buf=0x7ffdba6e4050, __fd=<optimized out>) at /usr/include/bits/unistd.h:44
#2  0x00007fe9af9ebb20 in g_wakeup_acknowledge (wakeup=0x1ed7330) at gwakeup.c:210
#3  0x00007fe9af9aa989 in g_main_context_check (context=context@entry=0x1f31ec0, max_priority=2147483647, fds=fds@entry=0x46ce330, n_fds=n_fds@entry=10) at gmain.c:3600
#4  0x00007fe9af9aade8 in g_main_context_iterate (context=context@entry=0x1f31ec0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3805
#5  0x00007fe9af9aaf6c in g_main_context_iteration (context=0x1f31ec0, may_block=1) at gmain.c:3869
#6  0x00007fe9b92c50ee in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=0x1ece110, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#7  0x00007fe9b86cd706 in QGuiEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#8  0x00007fe9b9296e7f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7ffdba6e4280, flags=...) at kernel/qeventloop.cpp:149
#9  0x00007fe9b9297175 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) (this=this@entry=0x7ffdba6e4280, flags=...) at kernel/qeventloop.cpp:204
#10 0x00007fe9b929c5c9 in QCoreApplication::exec() () at kernel/qcoreapplication.cpp:1225
#11 0x0000000000402f3f in  ()
#12 0x00007fe9b7bb48c5 in __libc_start_main (main=0x4024b0, argc=3, argv=0x7ffdba6e4858, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffdba6e4848) at libc-start.c:289
#13 0x0000000000403419 in _start ()

Reported using DrKonqi
Comment 1 Denis Kurz 2017-06-23 19:57:19 UTC
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 2 Denis Kurz 2018-01-31 16:50:33 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12, preferably more recent), please open a new one unless it already exists. Thank you for all your input.