Bug 351655 - Kmail Crash
Summary: Kmail Crash
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2015-08-23 16:51 UTC by alanlauer
Modified: 2018-01-31 16:51 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 alanlauer 2015-08-23 16:51:58 UTC
Application: kmail (4.14.9)
KDE Platform Version: 4.14.9 (Compiled from sources)
Qt Version: 4.8.6
Operating System: Linux 3.16.7-24-desktop x86_64
Distribution: "openSUSE 13.2 (Harlequin) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
I was replying to an email - I copied some text into the email from Dolphin - Selected a file name and copied/pasted it to the kmail reply.

The crash does not seem to be reproducible.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ff82e7bb800 (LWP 2037))]

Thread 4 (Thread 0x7ff808b25700 (LWP 2177)):
#0  0x00007ff82990505f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007ff81f002686 in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/libQtWebKit.so.4
#2  0x00007ff81f0026b9 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/libQtWebKit.so.4
#3  0x00007ff8299010a4 in start_thread () from /lib64/libpthread.so.0
#4  0x00007ff82bb0008d in clone () from /lib64/libc.so.6

Thread 3 (Thread 0x7ff7c376d700 (LWP 2202)):
#0  0x00007ff82990505f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007ff81ed74e7d in JSC::BlockAllocator::blockFreeingThreadMain() () from /usr/lib64/libQtWebKit.so.4
#2  0x00007ff81f02a1e6 in WTF::wtfThreadEntryPoint(void*) () from /usr/lib64/libQtWebKit.so.4
#3  0x00007ff8299010a4 in start_thread () from /lib64/libpthread.so.0
#4  0x00007ff82bb0008d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7ff7c295c700 (LWP 2225)):
#0  0x00007ff82baf7c5d in poll () from /lib64/libc.so.6
#1  0x00007ff82382ebe4 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007ff82382ecec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3  0x00007ff82d1520de in QEventDispatcherGlib::processEvents (this=0x7ff7b40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#4  0x00007ff82d123e6f in QEventLoop::processEvents (this=this@entry=0x7ff7c295bde0, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007ff82d124165 in QEventLoop::exec (this=this@entry=0x7ff7c295bde0, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007ff82d0210bf in QThread::exec (this=<optimized out>) at thread/qthread.cpp:538
#7  0x00007ff82d02379f in QThreadPrivate::start (arg=0x1c82370) at thread/qthread_unix.cpp:349
#8  0x00007ff8299010a4 in start_thread () from /lib64/libpthread.so.0
#9  0x00007ff82bb0008d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7ff82e7bb800 (LWP 2037)):
[KCrash Handler]
#6  0x00007ff82d0262e1 in QByteArray::append (this=0x5177058, ba=...) at tools/qbytearray.cpp:1619
#7  0x00007ff82d1391fa in QMetaObject::activate (sender=sender@entry=0x51883c0, m=m@entry=0x7ff828d441a0 <KIO::TransferJob::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe64b008b0) at kernel/qobject.cpp:3576
#8  0x00007ff82899b274 in KIO::TransferJob::data (this=this@entry=0x51883c0, _t1=_t1@entry=0x51883c0, _t2=...) at /usr/src/debug/kdelibs-4.14.9/build/kio/jobclasses.moc:446
#9  0x00007ff82899db59 in KIO::TransferJob::slotData (this=0x51883c0, _data=...) at /usr/src/debug/kdelibs-4.14.9/kio/kio/job.cpp:999
#10 0x00007ff82d1391fa in QMetaObject::activate (sender=0x3985de0, m=m@entry=0x7ff828d48560 <KIO::SlaveInterface::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7ffe64b00a60) at kernel/qobject.cpp:3576
#11 0x00007ff828a3c672 in KIO::SlaveInterface::data (this=<optimized out>, _t1=...) at /usr/src/debug/kdelibs-4.14.9/build/kio/slaveinterface.moc:159
#12 0x00007ff828a3dfd0 in KIO::SlaveInterface::dispatch (this=<optimized out>, _cmd=100, rawdata=...) at /usr/src/debug/kdelibs-4.14.9/kio/kio/slaveinterface.cpp:164
#13 0x00007ff828a3b74e in KIO::SlaveInterface::dispatch (this=0x3985de0) at /usr/src/debug/kdelibs-4.14.9/kio/kio/slaveinterface.cpp:92
#14 0x00007ff828a30466 in KIO::Slave::gotInput (this=0x3985de0) at /usr/src/debug/kdelibs-4.14.9/kio/kio/slave.cpp:344
#15 0x00007ff82d1391fa in QMetaObject::activate (sender=0x4c52240, m=m@entry=0x7ff828d41a80 <KIO::Connection::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x0) at kernel/qobject.cpp:3576
#16 0x00007ff82896cd00 in KIO::Connection::readyRead (this=<optimized out>) at /usr/src/debug/kdelibs-4.14.9/build/kio/connection.moc:105
#17 0x00007ff82896d3f1 in KIO::ConnectionPrivate::dequeue (this=0x4c43cd0) at /usr/src/debug/kdelibs-4.14.9/kio/kio/connection.cpp:82
#18 0x00007ff82d13d59e in QObject::event (this=0x4c52240, e=<optimized out>) at kernel/qobject.cpp:1231
#19 0x00007ff82c4be76c in QApplicationPrivate::notify_helper (this=this@entry=0x162b3a0, receiver=receiver@entry=0x4c52240, e=e@entry=0x3d36bf0) at kernel/qapplication.cpp:4565
#20 0x00007ff82c4c4cad in QApplication::notify (this=this@entry=0x7ffe64b01760, receiver=receiver@entry=0x4c52240, e=e@entry=0x3d36bf0) at kernel/qapplication.cpp:4351
#21 0x00007ff82e22ae0a in KApplication::notify (this=0x7ffe64b01760, receiver=0x4c52240, event=0x3d36bf0) at /usr/src/debug/kdelibs-4.14.9/kdeui/kernel/kapplication.cpp:311
#22 0x00007ff82d1252ad in QCoreApplication::notifyInternal (this=0x7ffe64b01760, receiver=receiver@entry=0x4c52240, event=event@entry=0x3d36bf0) at kernel/qcoreapplication.cpp:953
#23 0x00007ff82d12857d in sendEvent (event=0x3d36bf0, receiver=0x4c52240) at kernel/qcoreapplication.h:231
#24 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x15c5860) at kernel/qcoreapplication.cpp:1577
#25 0x00007ff82d128a23 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1470
#26 0x00007ff82d1528fe in sendPostedEvents () at kernel/qcoreapplication.h:236
#27 postEventSourceDispatch (s=0x163b4f0) at kernel/qeventdispatcher_glib.cpp:300
#28 0x00007ff82382ea04 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#29 0x00007ff82382ec48 in ?? () from /usr/lib64/libglib-2.0.so.0
#30 0x00007ff82382ecec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#31 0x00007ff82d1520be in QEventDispatcherGlib::processEvents (this=0x15cb100, flags=...) at kernel/qeventdispatcher_glib.cpp:450
#32 0x00007ff82c55b676 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#33 0x00007ff82d123e6f in QEventLoop::processEvents (this=this@entry=0x7ffe64b013b0, flags=...) at kernel/qeventloop.cpp:149
#34 0x00007ff82d124165 in QEventLoop::exec (this=this@entry=0x7ffe64b013b0, flags=...) at kernel/qeventloop.cpp:204
#35 0x00007ff82d1295b9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1225
#36 0x0000000000402f3f in ?? ()
#37 0x00007ff82ba3cb05 in __libc_start_main () from /lib64/libc.so.6
#38 0x0000000000403414 in _start ()

Reported using DrKonqi
Comment 1 Denis Kurz 2017-06-23 20:20:05 UTC
This bug has never been confirmed for a Kontact version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.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 opportunity 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:51:51 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.