Bug 322614 - Kmail crashed when loading large mail list folder, and trying to open folder settings
Summary: Kmail crashed when loading large mail list folder, and trying to open folder ...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.10.5
Platform: Debian unstable Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2013-07-20 12:37 UTC by Thomas Fjellstrom
Modified: 2017-01-07 22:31 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 Thomas Fjellstrom 2013-07-20 12:37:45 UTC
Application: kmail (4.10.5)
KDE Platform Version: 4.10.5
Qt Version: 4.8.5
Operating System: Linux 3.9-1-amd64 x86_64
Distribution: Debian GNU/Linux unstable (sid)

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

I selected a large mailing list folder (lkml), and while it was loading the index, I tried to open the settings/properties for the folder and the mailing list config for it. eventually it just crashed. context menu for the folder also quickly flashed repeatedly which made it hard to select an option.

-- Backtrace:
Application: KMail (kmail), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f6883a28780 (LWP 3007))]

Thread 3 (Thread 0x7f6861bd5700 (LWP 3011)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007f68752bfae2 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x00007f68752bfb19 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x00007f687e654e0e in start_thread (arg=0x7f6861bd5700) at pthread_create.c:311
#4  0x00007f6880d8393d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 2 (Thread 0x7f68612d4700 (LWP 3012)):
#0  0x00007f6878d3ffdd in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007f6878d40289 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f6878d00707 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f6878d010b3 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f6878d0129c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f6881707d06 in QEventDispatcherGlib::processEvents (this=0x7f685c0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:427
#6  0x00007f68816d97bf in QEventLoop::processEvents (this=this@entry=0x7f68612d3df0, flags=...) at kernel/qeventloop.cpp:149
#7  0x00007f68816d9ab5 in QEventLoop::exec (this=this@entry=0x7f68612d3df0, flags=...) at kernel/qeventloop.cpp:204
#8  0x00007f68815d88cf in QThread::exec (this=<optimized out>) at thread/qthread.cpp:536
#9  0x00007f68815daf6f in QThreadPrivate::start (arg=0x15c1b30) at thread/qthread_unix.cpp:338
#10 0x00007f687e654e0e in start_thread (arg=0x7f68612d4700) at pthread_create.c:311
#11 0x00007f6880d8393d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 1 (Thread 0x7f6883a28780 (LWP 3007)):
[KCrash Handler]
#6  QMutex::lock (this=this@entry=0x257b8e00000049) at thread/qmutex.cpp:150
#7  0x00007f68816de6b9 in QCoreApplication::postEvent (receiver=0x1a862980, event=0x20a32010, priority=0) at kernel/qcoreapplication.cpp:1354
#8  0x00007f68816f30ae in QObject::event (this=0x1a862980, e=<optimized out>) at kernel/qobject.cpp:1194
#9  0x00007f6881c0a70c in QApplicationPrivate::notify_helper (this=this@entry=0x11440a0, receiver=receiver@entry=0x1a862980, e=e@entry=0x14cda290) at kernel/qapplication.cpp:4567
#10 0x00007f6881c10d80 in QApplication::notify (this=this@entry=0x7ffff3758e10, receiver=receiver@entry=0x1a862980, e=e@entry=0x14cda290) at kernel/qapplication.cpp:4353
#11 0x00007f6883448cfa in KApplication::notify (this=0x7ffff3758e10, receiver=0x1a862980, event=0x14cda290) at ../../kdeui/kernel/kapplication.cpp:311
#12 0x00007f68816dab5d in QCoreApplication::notifyInternal (this=0x7ffff3758e10, receiver=receiver@entry=0x1a862980, event=event@entry=0x14cda290) at kernel/qcoreapplication.cpp:949
#13 0x00007f68816de0bf in sendEvent (event=0x14cda290, receiver=0x1a862980) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#14 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x10e1220) at kernel/qcoreapplication.cpp:1573
#15 0x00007f68816de563 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1466
#16 0x00007f6881708423 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#17 postEventSourceDispatch (s=0x113f570) at kernel/qeventdispatcher_glib.cpp:280
#18 0x00007f6878d00ea6 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007f6878d011f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007f6878d0129c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007f6881707ce5 in QEventDispatcherGlib::processEvents (this=0x113fbb0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#22 0x00007f6881ca8846 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#23 0x00007f68816d97bf in QEventLoop::processEvents (this=this@entry=0x7ffff3758a90, flags=...) at kernel/qeventloop.cpp:149
#24 0x00007f68816d9ab5 in QEventLoop::exec (this=this@entry=0x7ffff3758a90, flags=...) at kernel/qeventloop.cpp:204
#25 0x00007f68816df0fb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1221
#26 0x0000000000402c89 in ?? ()
#27 0x00007f6880cbc995 in __libc_start_main (main=0x402280, argc=3, ubp_av=0x7ffff3759028, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffff3759018) at libc-start.c:260
#28 0x0000000000403124 in _start ()

Possible duplicates by query: bug 310060, bug 304376.

Reported using DrKonqi
Comment 1 Denis Kurz 2016-09-24 18:12:24 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Comment 2 Denis Kurz 2017-01-07 22:31:55 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.