Bug 294851 - Yet another mail crash
Summary: Yet another mail crash
Status: RESOLVED FIXED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: IMAP resource (show other bugs)
Version: 4.8
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Christian Mollekopf
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-26 09:52 UTC by happy
Modified: 2013-11-23 14:36 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (7.67 KB, text/plain)
2012-03-15 08:56 UTC, Cédric Bellegarde
Details

Note You need to log in before you can comment on or make changes to this bug.
Description happy 2012-02-26 09:52:01 UTC
Application: akonadi_imap_resource (4.8)
KDE Platform Version: 4.8.00 (4.8.0
Qt Version: 4.7.4
Operating System: Linux 3.0.0-16-generic i686
Distribution: Ubuntu 11.10

-- Information about the crash:
- What I was doing when the application crashed:

mail had been running for maybe four hours after a reboot, no connection status changes.  KMail app was not in active use.

-- Backtrace:
Application: happy.heyoka of type IMAP E-Mail Server (akonadi_imap_resource), signal: Segmentation fault
[Current thread is 1 (Thread 0xb7763710 (LWP 2351))]

Thread 2 (Thread 0xb61b6b70 (LWP 1472)):
#0  0x00363416 in __kernel_vsyscall ()
#1  0x039e940e in __GI___poll (fds=0xb4e07438, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:87
#2  0x01f5034b in g_poll () from /lib/i386-linux-gnu/libglib-2.0.so.0
#3  0x01f41896 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#4  0x01f41c2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#5  0x004f8b37 in QEventDispatcherGlib::processEvents (this=0x85a0e40, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#6  0x004c91dd in QEventLoop::processEvents (this=0xb61b62c0, flags=...) at kernel/qeventloop.cpp:149
#7  0x004c9421 in QEventLoop::exec (this=0xb61b62c0, flags=...) at kernel/qeventloop.cpp:201
#8  0x003cc90b in QThread::exec (this=0x84cbb40) at thread/qthread.cpp:498
#9  0x00af1d89 in ?? () from /usr/lib/libkimap.so.4
#10 0x003cf7b3 in QThreadPrivate::start (arg=0x84cbb40) at thread/qthread_unix.cpp:331
#11 0x00bf5d31 in start_thread (arg=0xb61b6b70) at pthread_create.c:304
#12 0x039f80ce in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130
Backtrace stopped: Not enough registers or memory available to unwind further

Thread 1 (Thread 0xb7763710 (LWP 2351)):
[KCrash Handler]
#7  0x004dc9b7 in QObject::thread (this=0x87128e8) at kernel/qobject.cpp:1393
#8  0x004e1352 in QObject::QObject (this=0xb5831a00, parent=0x87128e8) at kernel/qobject.cpp:732
#9  0x067f5bce in KJob::KJob (this=0xb5831a00, parent=0x87128e8) at ../../kdecore/jobs/kjob.cpp:50
#10 0x00ad62e1 in KIMAP::Job::Job(KIMAP::JobPrivate&) () from /usr/lib/libkimap.so.4
#11 0x00ae0dcb in KIMAP::ListJob::ListJob(KIMAP::Session*) () from /usr/lib/libkimap.so.4
#12 0x08090d28 in RetrieveCollectionsTask::doStart (this=0x8734310, session=0x87128e8) at ../../../resources/imap/retrievecollectionstask.cpp:91
#13 0x080890e7 in ResourceTask::onSessionRequested (this=0x8734310, requestId=163, session=0x87128e8, errorCode=0) at ../../../resources/imap/resourcetask.cpp:115
#14 0x080892b0 in ResourceTask::qt_metacall (this=0x8734310, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0xbf83018c) at ./resourcetask.moc:85
#15 0x08093903 in RetrieveCollectionsTask::qt_metacall (this=0x8734310, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbf83018c) at ./retrievecollectionstask.moc:76
#16 0x004d0b7d in metacall (argv=0xbf83018c, idx=4, cl=QMetaObject::InvokeMetaMethod, object=0x8734310) at kernel/qmetaobject.cpp:237
#17 QMetaObject::metacall (object=0x8734310, cl=QMetaObject::InvokeMetaMethod, idx=4, argv=0xbf83018c) at kernel/qmetaobject.cpp:232
#18 0x004dfa6a in QMetaObject::activate (sender=0x8591e10, m=0x80abe78, local_signal_index=1, argv=0xbf83018c) at kernel/qobject.cpp:3278
#19 0x080994ff in SessionPool::sessionRequestDone (this=0x8591e10, _t1=163, _t2=0x87128e8, _t3=0, _t4=...) at ./sessionpool.moc:140
#20 0x0809bced in SessionPool::processPendingRequests (this=0x8591e10) at ../../../resources/imap/sessionpool.cpp:246
#21 0x0809c178 in SessionPool::qt_metacall (this=0x8591e10, _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0x8591f60) at ./sessionpool.moc:116
#22 0x004d0b7d in metacall (argv=0x8591f60, idx=12, cl=QMetaObject::InvokeMetaMethod, object=0x8591e10) at kernel/qmetaobject.cpp:237
#23 QMetaObject::metacall (object=0x8591e10, cl=QMetaObject::InvokeMetaMethod, idx=12, argv=0x8591f60) at kernel/qmetaobject.cpp:232
#24 0x004db685 in QMetaCallEvent::placeMetaCall (this=0x873de68, object=0x8591e10) at kernel/qobject.cpp:535
#25 0x004e2b52 in QObject::event (this=0x8591e10, e=0x873de68) at kernel/qobject.cpp:1217
#26 0x00eaed84 in notify_helper (e=0x873de68, receiver=0x8591e10, this=0x846ad60) at kernel/qapplication.cpp:4486
#27 QApplicationPrivate::notify_helper (this=0x846ad60, receiver=0x8591e10, e=0x873de68) at kernel/qapplication.cpp:4458
#28 0x00eb4133 in QApplication::notify (this=0x873de68, receiver=0x8591e10, e=0x873de68) at kernel/qapplication.cpp:3886
#29 0x01cac011 in KApplication::notify (this=0xbf830960, receiver=0x8591e10, event=0x873de68) at ../../kdeui/kernel/kapplication.cpp:311
#30 0x004ca19e in QCoreApplication::notifyInternal (this=0xbf830960, receiver=0x8591e10, event=0x873de68) at kernel/qcoreapplication.cpp:787
#31 0x004cdf93 in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#32 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x8446d60) at kernel/qcoreapplication.cpp:1428
#33 0x004ce0ec in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1321
#34 0x004f86a4 in sendPostedEvents () at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#35 postEventSourceDispatch (s=0x8464ed0) at kernel/qeventdispatcher_glib.cpp:277
#36 0x01f4125f in g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
#37 0x01f41990 in ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
#38 0x01f41c2a in g_main_context_iteration () from /lib/i386-linux-gnu/libglib-2.0.so.0
#39 0x004f8ada in QEventDispatcherGlib::processEvents (this=0x8447c50, flags=...) at kernel/qeventdispatcher_glib.cpp:422
#40 0x00f66e7a in QGuiEventDispatcherGlib::processEvents (this=0x8447c50, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#41 0x004c91dd in QEventLoop::processEvents (this=0xbf8308c4, flags=...) at kernel/qeventloop.cpp:149
#42 0x004c9421 in QEventLoop::exec (this=0xbf8308c4, flags=...) at kernel/qeventloop.cpp:201
#43 0x004ce19d in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064
#44 0x00eac924 in QApplication::exec () at kernel/qapplication.cpp:3760
#45 0x002541c1 in Akonadi::ResourceBase::init(Akonadi::ResourceBase*) () from /usr/lib/libakonadi-kde.so.4
#46 0x0805e2a7 in Akonadi::ResourceBase::init<ImapResource> (argc=3, argv=0xbf830a34) at /usr/include/akonadi/resourcebase.h:188
#47 0x0805864b in main (argc=3, argv=0xbf830a34) at ../../../resources/imap/imapresource.cpp:605

Reported using DrKonqi
Comment 1 Cédric Bellegarde 2012-03-15 08:56:02 UTC
Created attachment 69636 [details]
New crash information added by DrKonqi

akonadi_imap_resource (4.8) on KDE Platform 4.8.1 (4.8.1) using Qt 4.8.0

Same here on Kubuntu with KDE 4.8.1 and on ArchLinux with KDE 4.8.1.

-- Backtrace (Reduced):
#7  0x00742547 in QObject::thread (this=0x8e15128) at kernel/qobject.cpp:1371
#8  0x007493b2 in QObject::QObject (this=0x91cfaf0, parent=0x8e15128) at kernel/qobject.cpp:725
#9  0x01defc9e in KJob::KJob (this=0x91cfaf0, parent=0x8e15128) at ../../kdecore/jobs/kjob.cpp:50
#10 0x001aa321 in KIMAP::Job::Job(KIMAP::JobPrivate&) () from /usr/lib/libkimap.so.4
#11 0x001c0fc8 in KIMAP::SelectJob::SelectJob(KIMAP::Session*) () from /usr/lib/libkimap.so.4
Comment 2 Kevin Ottens 2013-11-16 07:31:02 UTC
The IMAP resource has a new maintainer, reassigning to him.
Comment 3 Christian Mollekopf 2013-11-19 16:34:11 UTC
Does this still apply to >=4.11.3?
Comment 4 Cédric Bellegarde 2013-11-19 21:56:53 UTC
Fixed for me
Comment 5 happy 2013-11-23 03:38:45 UTC
(In reply to comment #3)
> Does this still apply to >=4.11.3?

I haven't experienced this lately (@ 4.11.2)