Summary: | akonadi crash for no apparent reason | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | p92 |
Component: | IMAP resource | Assignee: | Kevin Ottens <ervin> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | kdepim-bugs, p92, vkrause |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
p92
2011-05-19 13:36:14 UTC
>#7 0x00007f6dd204a030 in ?? () from /usr/lib/libkimap.so.4
>#8 0x00007f6dd204a329 in ?? () from /usr/lib/libkimap.so.4
If the crash is easily reproducible, please install the debug package for kdepimlibs and paste a better backtrace.
Created attachment 60604 [details]
New crash information added by DrKonqi
akonadi_imap_resource (0.1) on KDE Platform 4.6.3 (4.6.3) using Qt 4.7.2
- What I was doing when the application crashed:
I cannot reproduce at will, but this morning it crashed again so now I have the debug symbols installed :)
- Unusual behavior I noticed:
-- Backtrace (Reduced):
#6 _int_malloc (av=0x7f16cb2a41c0, bytes=<value optimized out>) at malloc.c:4439
#7 0x00007f16caf9131e in __libc_malloc (bytes=65536) at malloc.c:3660
#8 0x00007f16ce696218 in QByteArray::realloc (this=0x1c07368, alloc=65504) at tools/qbytearray.cpp:1428
#9 0x00007f16ce696339 in QByteArray::resize (this=0x1c07368, size=32768) at tools/qbytearray.cpp:1396
#10 0x00007f16cd709364 in reserve (this=0x1c29eb0) at ../../include/QtCore/private/../../../src/corelib/tools/qringbuffer_p.h:158
Pasting inline Thread 1 (Thread 0x7f16cf337780 (LWP 14006)): #0 __lll_lock_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:136 #1 0x00007f16ca8a85b4 in _L_lock_944 () from /lib/x86_64-linux-gnu/libpthread.so.0 #2 0x00007f16ca8a83ca in __pthread_mutex_lock (mutex=0x1d10ad8) at pthread_mutex_lock.c:61 #3 0x00007f16c9943925 in g_main_context_wakeup () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x00007f16ce77e43b in QCoreApplication::postEvent (receiver=0x7f16b40f0bb0, event=0x7f16b41963a0, priority=0) at kernel/qcoreapplication.cpp:1194 #5 0x00007f16ce783ff0 in QMetaMethod::invoke (this=<value optimized out>, object=0x7f16b40f0bb0, connectionType=Qt::QueuedConnection, returnValue=..., val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...) at kernel/qmetaobject.cpp:1618 #6 0x00007f16ce784ba8 in QMetaObject::invokeMethod (obj=0x7f16b40f0bb0, member=<value optimized out>, type=Qt::AutoConnection, ret=..., val0=..., val1=..., val2=..., val3=..., val4=..., val5=..., val6=..., val7=..., val8=..., val9=...) at kernel/qmetaobject.cpp:1151 #7 0x00007f16cd41e030 in invokeMethod (this=<value optimized out>, __in_chrg=<value optimized out>) at /usr/include/qt4/QtCore/qobjectdefs.h:424 #8 KIMAP::SessionThread::~SessionThread (this=<value optimized out>, __in_chrg=<value optimized out>) at ../../kimap/sessionthread.cpp:51 #9 0x00007f16cd41e329 in KIMAP::SessionThread::~SessionThread (this=0x7f16b40f0bb0, __in_chrg=<value optimized out>) at ../../kimap/sessionthread.cpp:56 #10 0x00007f16cd419ff9 in KIMAP::Session::~Session (this=0x7f16b4195530, __in_chrg=<value optimized out>) at ../../kimap/session.cpp:67 #11 0x00007f16cd41a029 in KIMAP::Session::~Session (this=0x7f16b4195530, __in_chrg=<value optimized out>) at ../../kimap/session.cpp:68 #12 0x00007f16ce78dc14 in QObjectPrivate::deleteChildren (this=0x7f16b40fbcb0) at kernel/qobject.cpp:1964 #13 0x00007f16ce7925f4 in QObject::~QObject (this=0x7f16b41a5720, __in_chrg=<value optimized out>) at kernel/qobject.cpp:946 #14 0x00000000004178e9 in ImapAccount::~ImapAccount (this=0x7f16b41a5720, __in_chrg=<value optimized out>) at ../../../resources/imap/imapaccount.cpp:121 #15 0x00007f16ce78f4c8 in QObject::event (this=0x7f16b41a5720, e=<value optimized out>) at kernel/qobject.cpp:1209 Is it still happening for you with 4.7.x? I've been unable to reproduce that one, it just works for me. In case you still experience this please feel free to reopen. In such a case, we would need much more information like the actual IMAP server used and so on. |