Bug 295726 - kmail crashes every now and then during checking mails
Summary: kmail crashes every now and then during checking mails
Status: RESOLVED DUPLICATE of bug 295474
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-10 23:04 UTC by JarD
Modified: 2012-03-30 13:37 UTC (History)
7 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (10.00 KB, text/plain)
2012-03-10 23:10 UTC, JarD
Details
New crash information added by DrKonqi (11.27 KB, text/plain)
2012-03-12 11:53 UTC, Gastón Martini
Details
New crash information added by DrKonqi (8.81 KB, text/plain)
2012-03-13 17:52 UTC, Alex Wright
Details
New crash information added by DrKonqi (13.79 KB, text/plain)
2012-03-18 11:59 UTC, Gerhard Hoogterp
Details
New crash information added by DrKonqi (7.85 KB, text/plain)
2012-03-22 09:05 UTC, Lukasz
Details
New crash information added by DrKonqi (8.45 KB, text/plain)
2012-03-28 05:00 UTC, Bryan Zimmerman
Details

Note You need to log in before you can comment on or make changes to this bug.
Description JarD 2012-03-10 23:04:23 UTC
Application: kontact (4.8.0)
KDE Platform Version: 4.8.1 (4.8.1)
Qt Version: 4.8.0
Operating System: Linux 3.0.0-16-generic x86_64
Distribution: Ubuntu 11.10

-- Information about the crash:
I was checking and sorting my mail. Every couple e-mails kmail crashes without any apparent reason: no matter if an email was in a plain text or html, had an attachement or not

The crash can be reproduced every time.

-- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
__lll_lock_wait_private () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:97
	in ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S
[Current thread is 1 (Thread 0x7f2ab9fe67c0 (LWP 1874))]

Thread 6 (Thread 0x7f2a9e8b5700 (LWP 1875)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007f2ab681cc2c in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x00007f2ab681cd59 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x00007f2ab1fe9efc in start_thread (arg=0x7f2a9e8b5700) at pthread_create.c:304
#4  0x00007f2ab752c59d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#5  0x0000000000000000 in ?? ()

Thread 5 (Thread 0x7f2a9df94700 (LWP 1876)):
#0  0x00007f2ab7520473 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007f2ab1b17f68 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f2ab1b18429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f2ab7c9ac06 in QEventDispatcherGlib::processEvents (this=0x1f4fd00, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:426
#4  0x00007f2ab7c6a3e2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f2ab7c6a637 in QEventLoop::exec (this=0x7f2a9df93dc0, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007f2ab7b6a067 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#7  0x00007f2ab7b6d08b in QThreadPrivate::start (arg=0x1f4f3d0) at thread/qthread_unix.cpp:298
#8  0x00007f2ab1fe9efc in start_thread (arg=0x7f2a9df94700) at pthread_create.c:304
#9  0x00007f2ab752c59d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#10 0x0000000000000000 in ?? ()

Thread 4 (Thread 0x7f2a4ceaa700 (LWP 1894)):
#0  0x00007f2ab1fec034 in __pthread_mutex_lock (mutex=0x3331478) at pthread_mutex_lock.c:61
#1  0x00007f2ab1b17023 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f2ab1b17dfd in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f2ab1b18429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f2ab7c9ac06 in QEventDispatcherGlib::processEvents (this=0x33308f0, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:426
#5  0x00007f2ab7c6a3e2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#6  0x00007f2ab7c6a637 in QEventLoop::exec (this=0x7f2a4cea9d90, flags=...) at kernel/qeventloop.cpp:204
#7  0x00007f2ab7b6a067 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#8  0x00007f2ab7c4a17f in QInotifyFileSystemWatcherEngine::run (this=0x33271b0) at io/qfilesystemwatcher_inotify.cpp:248
#9  0x00007f2ab7b6d08b in QThreadPrivate::start (arg=0x33271b0) at thread/qthread_unix.cpp:298
#10 0x00007f2ab1fe9efc in start_thread (arg=0x7f2a4ceaa700) at pthread_create.c:304
#11 0x00007f2ab752c59d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#12 0x0000000000000000 in ?? ()

Thread 3 (Thread 0x7f2a4dd35700 (LWP 1896)):
[KCrash Handler]
#6  malloc_consolidate (av=0x7f2a48000020) at malloc.c:5153
#7  0x00007f2ab74c4a4f in malloc_consolidate (av=0x7f2a48000020) at malloc.c:5115
#8  _int_malloc (av=0x7f2a48000020, bytes=65536) at malloc.c:4373
#9  0x00007f2ab74c73cd in __GI___libc_malloc (bytes=65536) at malloc.c:3660
#10 0x00007f2ab7b6f088 in QByteArray::realloc (this=0x7f2a98033118, alloc=65504) at tools/qbytearray.cpp:1452
#11 0x00007f2ab7b6f1a9 in QByteArray::resize (this=0x7f2a98033118, size=32768) at tools/qbytearray.cpp:1420
#12 0x00007f2ab2e1ea06 in reserve (bytes=2, this=0x7f2a980cea00) at ../../include/QtCore/private/../../../src/corelib/tools/qringbuffer_p.h:158
#13 QAbstractSocket::writeData (this=<optimized out>, data=0x7f2a4dd345ec "\021", size=2) at socket/qabstractsocket.cpp:2315
#14 0x00007f2ab7bfe4af in QIODevice::write (this=0x7f2a98033130, data=0x7f2a4dd345ec "\021", maxSize=<optimized out>) at io/qiodevice.cpp:1370
#15 0x00007f2aab94b095 in ?? () from /usr/lib/libsopranoclient.so.1
#16 0x00007f2aab95128a in ?? () from /usr/lib/libsopranoclient.so.1
#17 0x00007f2aab952a03 in ?? () from /usr/lib/libsopranoclient.so.1
#18 0x00007f2ab00cf0b2 in Nepomuk::MainModel::executeQuery (this=0x2617df0, query=..., language=Soprano::Query::QueryLanguageSparql, userQueryLanguage=...) at ../../nepomuk/core/nepomukmainmodel.cpp:212
#19 0x00007f2ab00bf083 in Nepomuk::ResourceData::load (this=0x7f2a98100320) at ../../nepomuk/core/resourcedata.cpp:417
#20 0x00007f2ab00bf95c in Nepomuk::ResourceData::property (this=0x7f2a98100320, uri=...) at ../../nepomuk/core/resourcedata.cpp:265
#21 0x00007f2ab00d3893 in Nepomuk::Resource::property (this=0x7f2a4dd34cc0, uri=...) at ../../nepomuk/core/resource.cpp:301
#22 0x00007f2a54dd17da in MessageCore::NepomukResourceRetrieverRunnable::run (this=0x3474130) at ../../messagecore/asyncnepomukresourceretriever.cpp:47
#23 0x00007f2ab7b605b2 in QThreadPoolThread::run (this=0x27333c0) at concurrent/qthreadpool.cpp:107
#24 0x00007f2ab7b6d08b in QThreadPrivate::start (arg=0x27333c0) at thread/qthread_unix.cpp:298
#25 0x00007f2ab1fe9efc in start_thread (arg=0x7f2a4dd35700) at pthread_create.c:304
#26 0x00007f2ab752c59d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#27 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f2a5043c700 (LWP 1900)):
#0  __lll_lock_wait_private () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:97
#1  0x00007f2ab74c962f in _L_lock_10501 () from /lib/x86_64-linux-gnu/libc.so.6
#2  0x00007f2ab74c79c1 in __GI___libc_free (mem=0x7f2a48000020) at malloc.c:3736
#3  0x00007f2ab2e1cfeb in QAbstractSocket::disconnectFromHostImplementation (this=0x7f2a48148708) at socket/qabstractsocket.cpp:2510
#4  0x00007f2ab2e1d67d in qt_static_metacall (_a=<optimized out>, _id=<optimized out>, _o=<optimized out>, _c=<optimized out>) at .moc/release-shared/moc_qabstractsocket.cpp:168
#5  QAbstractSocket::qt_static_metacall (_o=<optimized out>, _c=<optimized out>, _id=<optimized out>, _a=<optimized out>) at .moc/release-shared/moc_qabstractsocket.cpp:152
#6  0x00007f2ab7c73661 in QMetaMethod::invoke (this=0x7f2a5043b8c0, object=0x7f2a48148708, connectionType=Qt::DirectConnection, returnValue=..., val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...) at kernel/qmetaobject.cpp:1641
#7  0x00007f2ab7c75970 in QMetaObject::invokeMethod (obj=0x7f2a48148708, member=<optimized out>, type=Qt::DirectConnection, ret=..., val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...) at kernel/qmetaobject.cpp:1179
#8  0x00007f2ab2e188b4 in invokeMethod (val9=..., val8=..., val7=..., val6=..., val5=..., val4=..., val3=..., val2=..., val1=..., val0=..., type=Qt::DirectConnection, member=0x7f2ab2e53820 "disconnectFromHostImplementation", obj=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs.h:418
#9  QAbstractSocket::disconnectFromHost (this=<optimized out>) at socket/qabstractsocket.cpp:2474
#10 0x00007f2ab2e189e7 in QAbstractSocket::close (this=0x7f2a48148708) at socket/qabstractsocket.cpp:2452
#11 0x00007f2ab2e29e7b in QLocalSocket::close (this=<optimized out>) at socket/qlocalsocket_unix.cpp:436
#12 0x00007f2ab2e2293b in QLocalSocket::~QLocalSocket (this=0x7f2a4814ad00, __in_chrg=<optimized out>) at socket/qlocalsocket.cpp:348
#13 0x00007f2ab2e22989 in QLocalSocket::~QLocalSocket (this=0x7f2a4814ad00, __in_chrg=<optimized out>) at socket/qlocalsocket.cpp:353
#14 0x00007f2aab951d60 in ?? () from /usr/lib/libsopranoclient.so.1
#15 0x00007f2aab951df9 in ?? () from /usr/lib/libsopranoclient.so.1
#16 0x00007f2ab7b6b360 in QThreadStorageData::finish (p=0x31e2c68) at thread/qthreadstorage.cpp:203
#17 0x00007f2ab7b6beb7 in QThreadPrivate::finish (arg=0x31e1fe0) at thread/qthread_unix.cpp:321
#18 0x00007f2ab7b6d093 in ~__pthread_cleanup_class (this=<synthetic pointer>, __in_chrg=<optimized out>) at /usr/include/pthread.h:545
#19 ~__pthread_cleanup_class (this=<synthetic pointer>, __in_chrg=<optimized out>) at thread/qthread_unix.cpp:716
#20 QThreadPrivate::start (arg=0x31e1fe0) at thread/qthread_unix.cpp:273
#21 0x00007f2ab1fe9efc in start_thread (arg=0x7f2a5043c700) at pthread_create.c:304
#22 0x00007f2ab752c59d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#23 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f2ab9fe67c0 (LWP 1874)):
#0  __lll_lock_wait_private () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:97
#1  0x00007f2ab74c962f in _L_lock_10501 () from /lib/x86_64-linux-gnu/libc.so.6
#2  0x00007f2ab74c79c1 in __GI___libc_free (mem=0x7f2a48000020) at malloc.c:3736
#3  0x00007f2ab469491e in qMetaTypeDeleteHelper<QDBusMessage> (t=0x37e6bc0) at ../../include/QtCore/../../src/corelib/kernel/qmetatype.h:134
#4  0x00007f2ab7c7c009 in QMetaCallEvent::~QMetaCallEvent (this=0x2a88570, __in_chrg=<optimized out>) at kernel/qobject.cpp:509
#5  0x00007f2ab7c7c069 in QMetaCallEvent::~QMetaCallEvent (this=0x2a88570, __in_chrg=<optimized out>) at kernel/qobject.cpp:518
#6  0x00007f2ab7c6f3d3 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x1df3380) at kernel/qcoreapplication.cpp:1516
#7  0x00007f2ab7c9a773 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#8  postEventSourceDispatch (s=<optimized out>) at kernel/qeventdispatcher_glib.cpp:279
#9  0x00007f2ab1b17a5d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x00007f2ab1b18258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x00007f2ab1b18429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x00007f2ab7c9ab9f in QEventDispatcherGlib::processEvents (this=0x1df4c10, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:424
#13 0x00007f2ab870421e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=<optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#14 0x00007f2ab7c6a3e2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#15 0x00007f2ab7c6a637 in QEventLoop::exec (this=0x7fff1d4d07c0, flags=...) at kernel/qeventloop.cpp:204
#16 0x00007f2ab7c6f6c7 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148
#17 0x0000000000403629 in main (argc=1, argv=0x7fff1d4d0e58) at ../../../kontact/src/main.cpp:218

Possible duplicates by query: bug 295054, bug 284552.

Reported using DrKonqi
Comment 1 JarD 2012-03-10 23:10:06 UTC
Created attachment 69477 [details]
New crash information added by DrKonqi

kontact (4.8.0) on KDE Platform 4.8.1 (4.8.1) using Qt 4.8.0

And now again kmail crashed. This time it was enough to scroll the e-mail list. This program's became simply useless if it's even not possible to check one's mail.

-- Backtrace (Reduced):
#6  0x00007f1122790a14 in malloc_consolidate (av=0x7f1104000020) at malloc.c:5161
#7  0x00007f1122791a4f in malloc_consolidate (av=0x7f1104000020) at malloc.c:5115
#8  _int_malloc (av=0x7f1104000020, bytes=65536) at malloc.c:4373
#9  0x00007f11227943cd in __GI___libc_malloc (bytes=65536) at malloc.c:3660
#10 0x00007f1122e3c088 in QByteArray::realloc (this=0x7f1104009928, alloc=65504) at tools/qbytearray.cpp:1452
Comment 2 Gastón Martini 2012-03-12 11:53:50 UTC
Created attachment 69531 [details]
New crash information added by DrKonqi

kontact (4.8.0) on KDE Platform 4.8.1 (4.8.1) using Qt 4.8.0

- What I was doing when the application crashed:

I have just started Kontact with KMail opened. A few seconds after the window appeared, it crashed. It didn't give me time to run any command. There was no progress bar showing at the bottom.
KMail crashed several times after updating to 4.8, with no apparent cause.

-- Backtrace (Reduced):
#6  0x00007f9e0687ca14 in malloc_consolidate (av=0x7f9de8000020) at malloc.c:5161
#7  0x00007f9e0687da4f in malloc_consolidate (av=0x7f9de8000020) at malloc.c:5115
#8  _int_malloc (av=0x7f9de8000020, bytes=65536) at malloc.c:4373
#9  0x00007f9e068803cd in __GI___libc_malloc (bytes=65536) at malloc.c:3660
#10 0x00007f9e06f28088 in QByteArray::realloc (this=0x231c908, alloc=65504) at tools/qbytearray.cpp:1452
Comment 3 Gastón Martini 2012-03-12 12:17:28 UTC
(In reply to comment #2)
> Created attachment 69531 [details]
> New crash information added by DrKonqi
> 
> kontact (4.8.0) on KDE Platform 4.8.1 (4.8.1) using Qt 4.8.0
> 
> - What I was doing when the application crashed:
> 
> I have just started Kontact with KMail opened. A few seconds after the
> window appeared, it crashed. It didn't give me time to run any command.
> There was no progress bar showing at the bottom.
> KMail crashed several times after updating to 4.8, with no apparent cause.
> 
> -- Backtrace (Reduced):
> #6  0x00007f9e0687ca14 in malloc_consolidate (av=0x7f9de8000020) at
> malloc.c:5161
> #7  0x00007f9e0687da4f in malloc_consolidate (av=0x7f9de8000020) at
> malloc.c:5115
> #8  _int_malloc (av=0x7f9de8000020, bytes=65536) at malloc.c:4373
> #9  0x00007f9e068803cd in __GI___libc_malloc (bytes=65536) at malloc.c:3660
> #10 0x00007f9e06f28088 in QByteArray::realloc (this=0x231c908, alloc=65504)
> at tools/qbytearray.cpp:1452

Ok, I opened Kontact two more times, and two times it crashed. Then I opened KMail standalone and apparently it was working this time, I marked a few mails as read, changed folder and... it blocked (not crashed, blocked).
Right now KMail is unusable for me.

I forgot to report that I have 3 Gmail IMAP, 1 POP3 and 1 local mailbox accounts configured.
Comment 4 Alex Wright 2012-03-13 17:52:22 UTC
Created attachment 69584 [details]
New crash information added by DrKonqi

kontact (4.8.0) on KDE Platform 4.8.1 (4.8.1) using Qt 4.8.0

- What I was doing when the application crashed:

Clicking through the unread emails by selecting messages from the message list.

-- Backtrace (Reduced):
#9  0x00007f6de5863c07 in QByteArray::realloc (this=0x3754dc8, alloc=65504) at tools/qbytearray.cpp:1452
#10 0x00007f6de5863d28 in QByteArray::resize (this=0x3754dc8, size=32768) at tools/qbytearray.cpp:1420
#11 0x00007f6ddfe3eb50 in reserve (bytes=2, this=0x3484e20) at ../../include/QtCore/private/../../../src/corelib/tools/qringbuffer_p.h:158
#12 QAbstractSocket::writeData (this=<optimized out>, data=0x7f6d730d650c "\021", size=2) at socket/qabstractsocket.cpp:2315
#13 0x00007f6de58f2b56 in QIODevice::write (this=0x34faa10, data=0x7f6d730d650c "\021", maxSize=<optimized out>) at io/qiodevice.cpp:1370
Comment 5 Gerhard Hoogterp 2012-03-18 11:59:48 UTC
Created attachment 69708 [details]
New crash information added by DrKonqi

kontact (4.8.0) on KDE Platform 4.8.1 (4.8.1) using Qt 4.8.0

Just reading mails. Nothing special, but kontact crashes very often lately at unrelated moments.

-- Backtrace (Reduced):
#6  0x00007ff7cfc12a14 in malloc_consolidate (av=0x7ff7b0000020) at malloc.c:5161
#7  0x00007ff7cfc13a4f in malloc_consolidate (av=0x7ff7b0000020) at malloc.c:5115
#8  _int_malloc (av=0x7ff7b0000020, bytes=65536) at malloc.c:4373
#9  0x00007ff7cfc163cd in __GI___libc_malloc (bytes=65536) at malloc.c:3660
#10 0x00007ff7d02be088 in QByteArray::realloc (this=0x7ff7b0027658, alloc=65504) at tools/qbytearray.cpp:1452
Comment 6 Lukasz 2012-03-22 09:05:35 UTC
Created attachment 69801 [details]
New crash information added by DrKonqi

kontact (4.8.0) on KDE Platform 4.8.1 (4.8.1) using Qt 4.8.0

- What I was doing when the application crashed:

Just checking unreaded mail in different folders.

-- Backtrace (Reduced):
#10 0x00007fef73b988b0 in malloc_consolidate (av=0x7fef00000020) at malloc.c:4246
#11 0x00007fef73b99ec6 in malloc_consolidate (av=0x7fef00000020) at malloc.c:4215
#12 _int_malloc (av=0x7fef00000020, bytes=65536) at malloc.c:3532
#13 0x00007fef73b9ca45 in __GI___libc_malloc (bytes=65536) at malloc.c:2924
#14 0x00007fef74254fb8 in QByteArray::realloc (this=0x7fef0002b608, alloc=65504) at tools/qbytearray.cpp:1452
Comment 7 Bryan Zimmerman 2012-03-28 05:00:55 UTC
Created attachment 69956 [details]
New crash information added by DrKonqi

kontact (4.8.0) on KDE Platform 4.8.1 (4.8.1) using Qt 4.8.0

Clicked on an email to open it when the application crashed.

-- Backtrace (Reduced):
#7  0x050e727d in malloc_consolidate (av=0xb4a00010) at malloc.c:5161
#8  malloc_consolidate (av=0xb4a00010) at malloc.c:5089
#9  0x050e820c in _int_malloc (av=0xb4a00010, bytes=65536) at malloc.c:4373
#10 0x050ea7f8 in __GI___libc_malloc (bytes=65536) at malloc.c:3660
#11 0x00b321cb in qMalloc (size=65536) at global/qmalloc.cpp:55
Comment 8 Jörg Schaible 2012-03-28 06:04:16 UTC
Can you open the system monitor before starting KMail and check the memory consumption of it after its start? If it tries to grab all available memory and finally crashes, you're probably facing the consequences of a filter bug of the old version described in bug 289277. You might have now mails in your folders each with 100MB and more and KMail simply runs out of resources now.
Comment 9 Christophe Marin 2012-03-30 13:37:51 UTC

*** This bug has been marked as a duplicate of bug 295474 ***