Bug 281061 - akonadi ressource crashed
Summary: akonadi ressource crashed
Status: RESOLVED WORKSFORME
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: IMAP resource (show other bugs)
Version: 4.7
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Christian Mollekopf
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2011-08-30 18:56 UTC by H.H.
Modified: 2018-10-27 02:40 UTC (History)
3 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 H.H. 2011-08-30 18:56:15 UTC
Application: akonadi_imap_resource (4.7)
KDE Platform Version: 4.7.00 (4.7.0) "release 6"
Qt Version: 4.7.3
Operating System: Linux 2.6.37.1-1.2-desktop x86_64
Distribution: "openSUSE 11.4 (x86_64)"

-- Information about the crash:
What I was doing when  the application crashed: I browsed with chromium.

-- Backtrace:
Application: Akonadi Resource (akonadi_imap_resource), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f95da67e760 (LWP 2694))]

Thread 3 (Thread 0x7f95c97a0700 (LWP 3676)):
#0  0x00007f95d6195503 in poll () from /lib64/libc.so.6
#1  0x00007f95d4af3d14 in ?? () from /lib64/libglib-2.0.so.0
#2  0x00007f95d4af4250 in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#3  0x00007f95d9b4822f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#4  0x00007f95d9b1c8d2 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#5  0x00007f95d9b1cae5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#6  0x00007f95d9a317a4 in QThread::exec() () from /usr/lib64/libQtCore.so.4
#7  0x00007f95d87a91e3 in KIMAP::SessionThread::run() () from /usr/lib64/libkimap.so.4
#8  0x00007f95d9a34095 in ?? () from /usr/lib64/libQtCore.so.4
#9  0x00007f95d5a5aa3f in start_thread () from /lib64/libpthread.so.0
#10 0x00007f95d619e67d in clone () from /lib64/libc.so.6
#11 0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f95c2e54700 (LWP 3677)):
#0  0x00007f95d5a5f6f9 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f95d9a346e2 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQtCore.so.4
#2  0x00007f95d9a28f38 in ?? () from /usr/lib64/libQtCore.so.4
#3  0x00007f95d9a34095 in ?? () from /usr/lib64/libQtCore.so.4
#4  0x00007f95d5a5aa3f in start_thread () from /lib64/libpthread.so.0
#5  0x00007f95d619e67d in clone () from /lib64/libc.so.6
#6  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f95da67e760 (LWP 2694)):
[KCrash Handler]
#6  0x00007f95d9b483c4 in QEventDispatcherGlib::wakeUp() () from /usr/lib64/libQtCore.so.4
#7  0x00007f95d9b2047b in QCoreApplication::postEvent(QObject*, QEvent*, int) () from /usr/lib64/libQtCore.so.4
#8  0x00007f95d9b25a0f in QMetaMethod::invoke(QObject*, Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) const () from /usr/lib64/libQtCore.so.4
#9  0x00007f95d9b26e00 in QMetaObject::invokeMethod(QObject*, char const*, Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) () from /usr/lib64/libQtCore.so.4
#10 0x00007f95d87af132 in KIMAP::SessionThread::~SessionThread() () from /usr/lib64/libkimap.so.4
#11 0x00007f95d87af289 in KIMAP::SessionThread::~SessionThread() () from /usr/lib64/libkimap.so.4
#12 0x00007f95d87a7679 in KIMAP::Session::~Session() () from /usr/lib64/libkimap.so.4
#13 0x00007f95d87a76a9 in KIMAP::Session::~Session() () from /usr/lib64/libkimap.so.4
#14 0x00007f95d9b313a8 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4
#15 0x00007f95d8ee5144 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#16 0x00007f95d8eed6fa in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#17 0x00007f95d7068736 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#18 0x00007f95d9b1d47c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#19 0x00007f95d9b20c75 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQtCore.so.4
#20 0x00007f95d9b48093 in ?? () from /usr/lib64/libQtCore.so.4
#21 0x00007f95d4af37d3 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#22 0x00007f95d4af3fb0 in ?? () from /lib64/libglib-2.0.so.0
#23 0x00007f95d4af4250 in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#24 0x00007f95d9b4822f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#25 0x00007f95d8f8abae in ?? () from /usr/lib64/libQtGui.so.4
#26 0x00007f95d9b1c8d2 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#27 0x00007f95d9b1cae5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#28 0x00007f95d9b20f2b in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#29 0x00007f95da154ca7 in Akonadi::ResourceBase::init(Akonadi::ResourceBase*) () from /usr/lib64/libakonadi-kde.so.4
#30 0x0000000000419068 in main ()

Reported using DrKonqi
Comment 1 Kevin Ottens 2011-09-17 16:07:30 UTC
I will need more information for that one, namely:
 * the rought amount of mail
 * the mail server used
 * was there any network connectivity issue

Also to debug that kind of cases efficiently, I'd need to be provided with some idea of the IMAP traffic which created the issue. That can be done by setting the KIMAP_LOGFILE environment variable and restarting the akonadiserver.

For instance:
export KIMAP_LOGFILE=imaplog
akonadictl restart

Look at the pid of the imap resource you should then have a couple of imaplog.pid.* files. Wait for the crash, and then provide me what happened before the crash. It's the best way for me to create a test case that I can reproduce here. Only caveat though is that some private data is likely in the log (except the authentication phase, after that it logs everything) so you'd have to trust me with your data and send it privately.
Comment 2 Kevin Ottens 2013-11-16 07:30:52 UTC
The IMAP resource has a new maintainer, reassigning to him.
Comment 3 Andrew Crouthamel 2018-09-26 22:23:36 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 4 Andrew Crouthamel 2018-10-27 02:40:22 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!