Bug 339395 - akonadi_imap_resource often segfaults after adding a gmail account in Kmail a few days
Summary: akonadi_imap_resource often segfaults after adding a gmail account in Kmail a...
Status: RESOLVED DUPLICATE of bug 351850
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: IMAP resource (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Christian Mollekopf
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-25 19:25 UTC by V字龍(Vdragon)
Modified: 2016-03-21 23:47 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (5.18 KB, text/plain)
2014-11-06 14:29 UTC, Luis Lezcano Airaldi
Details

Note You need to log in before you can comment on or make changes to this bug.
Description V字龍(Vdragon) 2014-09-25 19:25:09 UTC
I added a gmail account in Kmail a few days ago, and I noticed akonadi_imap_resource segfaults  a few times lately itself.

The crash can be reproduced sometimes.

-- Backtrace:
Application: 型態為 IMAP 信件伺服器 的 Vdragon.Taiwan@gmail.com (akonadi_imap_resource), signal: Segmentation fault
Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0xb4b72740 (LWP 24169))]

Thread 3 (Thread 0xb1a72b40 (LWP 24174)):
#0  0xb77b4d7c in __kernel_vsyscall ()
#1  0xb578b56b in poll () from /lib/i386-linux-gnu/libc.so.6
#2  0xb552920b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0xb551a3e8 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0xb551a528 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0xb739795f in QEventDispatcherGlib::processEvents (this=0xb1100468, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#6  0xb7366823 in QEventLoop::processEvents (this=this@entry=0xb1a72288, flags=...) at kernel/qeventloop.cpp:149
#7  0xb7366b49 in QEventLoop::exec (this=this@entry=0xb1a72288, flags=...) at kernel/qeventloop.cpp:204
#8  0xb725323d in QThread::exec (this=this@entry=0x91693a8) at thread/qthread.cpp:537
#9  0xb725338b in QThread::run (this=0x91693a8) at thread/qthread.cpp:604
#10 0xb7255b6f in QThreadPrivate::start (arg=0x91693a8) at thread/qthread_unix.cpp:349
#11 0xb5605f70 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#12 0xb579a4ce in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 2 (Thread 0xb10ffb40 (LWP 25401)):
#0  0xb7236530 in __x86.get_pc_thunk.bx () from /usr/lib/i386-linux-gnu/libQtCore.so.4
#1  0xb739928b in QTimerInfoList::timerWait (this=0xb070334c, tm=...) at kernel/qeventdispatcher_unix.cpp:459
#2  0xb739782b in timerSourcePrepareHelper (src=<optimized out>, timeout=0xb10ff11c) at kernel/qeventdispatcher_glib.cpp:143
#3  0xb73978bd in timerSourcePrepare (source=0xb0703318, timeout=0xb10ff11c) at kernel/qeventdispatcher_glib.cpp:176
#4  0xb55199b3 in g_main_context_prepare () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0xb551a2df in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#6  0xb551a528 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#7  0xb739795f in QEventDispatcherGlib::processEvents (this=0xb0702a50, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#8  0xb7366823 in QEventLoop::processEvents (this=this@entry=0xb10ff288, flags=...) at kernel/qeventloop.cpp:149
#9  0xb7366b49 in QEventLoop::exec (this=this@entry=0xb10ff288, flags=...) at kernel/qeventloop.cpp:204
#10 0xb725323d in QThread::exec (this=this@entry=0x90fd758) at thread/qthread.cpp:537
#11 0xb725338b in QThread::run (this=0x90fd758) at thread/qthread.cpp:604
#12 0xb7255b6f in QThreadPrivate::start (arg=0x90fd758) at thread/qthread_unix.cpp:349
#13 0xb5605f70 in start_thread () from /lib/i386-linux-gnu/libpthread.so.0
#14 0xb579a4ce in clone () from /lib/i386-linux-gnu/libc.so.6

Thread 1 (Thread 0xb4b72740 (LWP 24169)):
[KCrash Handler]
#7  0xb6237c04 in QByteArray (a=..., this=0xbfc31418) at /usr/include/qt4/QtCore/qbytearray.h:439
#8  toString (this=0x0) at ../../kimap/message_p.h:42
#9  KIMAP::SearchJob::handleResponse (this=0x91a0980, response=...) at ../../kimap/searchjob.cpp:429
#10 0xb622774e in KIMAP::SessionPrivate::responseReceived (this=0x90883c0, response=...) at ../../kimap/session.cpp:300
#11 0xb6229fcb in KIMAP::SessionPrivate::qt_static_metacall (_o=0x0, _id=0, _a=0xb072fa70, _c=<optimized out>) at ./moc_session_p.cpp:77
#12 0xb73798aa in QMetaCallEvent::placeMetaCall (this=0xb072f9b0, object=0x90883c0) at kernel/qobject.cpp:524
#13 0xb73816fb in QObject::event (this=0x90883c0, e=0xb072f9b0) at kernel/qobject.cpp:1194
#14 0xb68737f4 in QApplicationPrivate::notify_helper (this=0x907be38, receiver=0x90883c0, e=0xb072f9b0) at kernel/qapplication.cpp:4567
#15 0xb687a2d3 in QApplication::notify (this=0xbfc31b64, receiver=receiver@entry=0x90883c0, e=e@entry=0xb072f9b0) at kernel/qapplication.cpp:4353
#16 0xb5e6a1f4 in KApplication::notify (this=0xbfc31b64, receiver=0x90883c0, event=0xb072f9b0) at ../../kdeui/kernel/kapplication.cpp:311
#17 0xb7367e4a in QCoreApplication::notifyInternal (this=0xbfc31b64, receiver=receiver@entry=0x90883c0, event=event@entry=0xb072f9b0) at kernel/qcoreapplication.cpp:953
#18 0xb736b70d in sendEvent (event=0xb072f9b0, receiver=0x90883c0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231
#19 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x9053fd8) at kernel/qcoreapplication.cpp:1577
#20 0xb736bc1c in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1470
#21 0xb739823e in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:236
#22 postEventSourceDispatch (s=0x908ba00) at kernel/qeventdispatcher_glib.cpp:287
#23 0xb551a1e3 in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
#24 0xb551a468 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#25 0xb551a528 in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#26 0xb739793b in QEventDispatcherGlib::processEvents (this=this@entry=0x9054ba0, flags=...) at kernel/qeventdispatcher_glib.cpp:434
#27 0xb69285de in QGuiEventDispatcherGlib::processEvents (this=0x9054ba0, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#28 0xb7366823 in QEventLoop::processEvents (this=this@entry=0xbfc31ad8, flags=...) at kernel/qeventloop.cpp:149
#29 0xb7366b49 in QEventLoop::exec (this=this@entry=0xbfc31ad8, flags=...) at kernel/qeventloop.cpp:204
#30 0xb736c8fe in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1225
#31 0xb6871a24 in QApplication::exec () at kernel/qapplication.cpp:3828
#32 0xb763b3c8 in Akonadi::ResourceBase::init (r=r@entry=0x91c2a78) at ../../akonadi/resourcebase.cpp:570
#33 0x0805b4dd in Akonadi::ResourceBase::init<ImapResource> (argc=argc@entry=3, argv=argv@entry=0xbfc31c44) at /usr/include/akonadi/resourcebase.h:193
#34 0x0805ac0b in main (argc=3, argv=0xbfc31c44) at ../../../resources/imap/main.cpp:22


Reproducible: Sometimes

Steps to Reproduce:
N/A

Actual Results:  
N/A

Expected Results:  
N/A

N/A
Comment 1 Luis Lezcano Airaldi 2014-11-06 14:29:52 UTC
Created attachment 89477 [details]
New crash information added by DrKonqi

akonadi_imap_resource (4.14) on KDE Platform 4.14.2 using Qt 4.8.6

- What I was doing when the application crashed:

KMail was in the systray, and it seems that in a mail check it crashed

-- Backtrace (Reduced):
#5  0x00007f94e513464d in KIMAP::SearchJob::handleResponse(KIMAP::Message const&) () at /usr/lib64/libkimap.so.4
#6  0x00007f94e5124ddc in KIMAP::SessionPrivate::responseReceived(KIMAP::Message const&) () at /usr/lib64/libkimap.so.4
#7  0x00007f94e74e159e in QObject::event(QEvent*) () at /usr/lib64/libQtCore.so.4
#8  0x00007f94e686276c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4
#9  0x00007f94e6868cad in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQtGui.so.4
Comment 2 Matěj Laitl 2014-12-18 12:23:26 UTC
This looks like a duplicate of bug 340157 to me. I'd like to mark it as such in a couple of days if there are no objections.
Comment 3 Daniel Vrátil 2016-03-21 23:47:33 UTC

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