Bug 244865 - IMAP Resource crash after listing/fetching folders
Summary: IMAP Resource crash after listing/fetching folders
Status: RESOLVED WORKSFORME
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: IMAP resource (show other bugs)
Version: 1.3.50
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Christian Mollekopf
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2010-07-16 15:38 UTC by Leo Franchi
Modified: 2018-10-27 02:18 UTC (History)
2 users (show)

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 Leo Franchi 2010-07-16 15:38:27 UTC
Version:           1.3.50 (using Devel) 
OS:                Linux

After starting akonadi, after a while the IMAP resource crashes with this backtrace:



Thread 1 (Thread 0x7f8dd3449760 (LWP 6724)):
[KCrash Handler]
#6  0x00007f8dce10f565 in raise () from /lib/libc.so.6
#7  0x00007f8dce1109e6 in abort () from /lib/libc.so.6
#8  0x00007f8dd273d999 in qt_message_output (msgType=QtFatalMsg, buf=0x189c9488 "ASSERT: \"separator.size()==1\" in file /home/leo/kde/src/kdepimlibs/kimap/listjob.cpp, line 163")
    at global/qglobal.cpp:2259
#9  0x00007f8dd273da44 in qt_message (msgType=QtFatalMsg, msg=0x7f8dd28c5c88 "ASSERT: \"%s\" in file %s, line %d", ap=0x7fff34a01ea0) at global/qglobal.cpp:2305
#10 0x00007f8dd273e13e in qFatal (msg=0x7f8dd28c5c88 "ASSERT: \"%s\" in file %s, line %d") at global/qglobal.cpp:2488
#11 0x00007f8dd273d599 in qt_assert (assertion=0x7f8dd1085d77 "separator.size()==1", file=0x7f8dd1085d48 "/home/leo/kde/src/kdepimlibs/kimap/listjob.cpp", line=163) at global/qglobal.cpp:2004
#12 0x00007f8dd1060c0e in KIMAP::ListJob::handleResponse (this=0x2839ec0, response=...) at /home/leo/kde/src/kdepimlibs/kimap/listjob.cpp:163
#13 0x00007f8dd106be2a in KIMAP::SessionPrivate::responseReceived (this=0x28a0fd0, response=...) at /home/leo/kde/src/kdepimlibs/kimap/session.cpp:253
#14 0x00007f8dd106cd79 in KIMAP::Session::qt_metacall (this=0x2884da0, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0x2828b50) at /home/leo/kde/build/kdepimlibs/kimap/session.moc:106
#15 0x00007f8dd2857ff5 in QMetaObject::metacall (object=0x2884da0, cl=QMetaObject::InvokeMetaMethod, idx=9, argv=0x2828b50) at kernel/qmetaobject.cpp:237
#16 0x00007f8dd2865e7a in QMetaCallEvent::placeMetaCall (this=0xb865240, object=0x2884da0) at kernel/qobject.cpp:534
#17 0x00007f8dd2866f37 in QObject::event (this=0x2884da0, e=0xb865240) at kernel/qobject.cpp:1208
#18 0x00007f8dd1814532 in QApplicationPrivate::notify_helper (this=0x26b2a10, receiver=0x2884da0, e=0xb865240) at kernel/qapplication.cpp:4392
#19 0x00007f8dd1811c5c in QApplication::notify (this=0x7fff34a03020, receiver=0x2884da0, e=0xb865240) at kernel/qapplication.cpp:3794
#20 0x00007f8dcf819bfd in KApplication::notify (this=0x7fff34a03020, receiver=0x2884da0, event=0xb865240) at /home/leo/kde/src/kdelibs/kdeui/kernel/kapplication.cpp:309
#21 0x00007f8dd2850b03 in QCoreApplication::notifyInternal (this=0x7fff34a03020, receiver=0x2884da0, event=0xb865240) at kernel/qcoreapplication.cpp:732
#22 0x00007f8dd2854157 in QCoreApplication::sendEvent (receiver=0x2884da0, event=0xb865240) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#23 0x00007f8dd2851cbd in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x2672720) at kernel/qcoreapplication.cpp:1370
#24 0x00007f8dd28518df in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1266
#25 0x00007f8dd288515d in QCoreApplication::sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#26 0x00007f8dd28841fe in postEventSourceDispatch (s=0x26b6610) at kernel/qeventdispatcher_glib.cpp:277
#27 0x00007f8dcd1a3b33 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#28 0x00007f8dcd1a4310 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0
#29 0x00007f8dcd1a45ad in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#30 0x00007f8dd2884a05 in QEventDispatcherGlib::processEvents (this=0x2671dd0, flags=...) at kernel/qeventdispatcher_glib.cpp:415
#31 0x00007f8dd18da89a in QGuiEventDispatcherGlib::processEvents (this=0x2671dd0, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#32 0x00007f8dd284ea9a in QEventLoop::processEvents (this=0x7fff34a02f90, flags=...) at kernel/qeventloop.cpp:149
#33 0x00007f8dd284ebee in QEventLoop::exec (this=0x7fff34a02f90, flags=...) at kernel/qeventloop.cpp:197
#34 0x00007f8dd28511c2 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#35 0x00007f8dd18117d4 in QApplication::exec () at kernel/qapplication.cpp:3668
#36 0x00007f8dd2f886ec in Akonadi::ResourceBase::init (r=0x28582b0) at /home/leo/kde/src/kdepimlibs/akonadi/resourcebase.cpp:245
#37 0x000000000042ba53 in Akonadi::ResourceBase::init<ImapResource> (argc=3, argv=0x7fff34a03178) at /home/leo/kde/include/akonadi/resourcebase.h:186
#38 0x00000000004250a8 in main (argc=3, argv=0x7fff34a03178) at /home/leo/kde/src/kdepim/runtime/resources/imap/imapresource.cpp:2027


Reproducible: Sometimes
Comment 1 Leo Franchi 2010-07-16 20:30:08 UTC
kevin, here's the KIMAP_LOGFILE.

i don't see much of use, nothing seems like out of the ordinary. this is the contents of the file *after* the imap resource crashed:

http://officespace.kdab.com/~leo/kimap.log2
Comment 2 Leo Franchi 2010-07-16 20:41:03 UTC
uh.... i meant contents of the file *after*
Comment 3 Kevin Ottens 2010-07-19 09:35:45 UTC
No really you meant *before*. :-)

Anyway, tried to use this log to reproduce the crash without success. From the log I fail to see how that could happen... The logger tries hard to be as transparent as possible, but it's not 100% transparent. Could you try producing such a log with something lower level like wireshark? (obviously mean you'd better not use SSL while testing).
Comment 4 Kevin Ottens 2013-11-16 07:27:13 UTC
The IMAP resource has a new maintainer, reassigning to him.
Comment 5 Andrew Crouthamel 2018-09-25 03:49:49 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Andrew Crouthamel 2018-10-27 02:18:10 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!