Bug 341456 - akonadi imap resource crashed when trying to move many emails to subfolder
Summary: akonadi imap resource crashed when trying to move many emails to subfolder
Status: RESOLVED FIXED
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: drkonqi
: 341528 (view as bug list)
Depends on:
Blocks:
 
Reported: 2014-12-01 11:09 UTC by Martin Tlustos
Modified: 2017-06-25 16:15 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Tlustos 2014-12-01 11:09:30 UTC
Application: akonadi_imap_resource (4.14)
KDE Platform Version: 4.14.1
Qt Version: 4.8.6
Operating System: Linux 3.16.0-25-generic x86_64
Distribution: Ubuntu 14.10

-- Information about the crash:
- What I was doing when the application crashed:
trying to move many (>3.000) mails to a newly created subfolder on my google account.
- Unusual behavior I noticed:
the imap resource had gotten stuck at syncing this specific folder (Sent mail) on the google account.
- Custom settings of the application:
I created a subfolder (old sent mail) under my "Sent mail" folder for archiving.

-- Backtrace:
Application: Persönlich vom Typ IMAP-E-Mail-Server (akonadi_imap_resource), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7ff3f706b8c0 (LWP 9545))]

Thread 2 (Thread 0x7ff3e2ade700 (LWP 9547)):
#0  0x00007ff3f294539d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007ff3f18c0ee4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007ff3f18c0ffc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007ff3f668704e in QEventDispatcherGlib::processEvents (this=0x7ff3dc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#4  0x00007ff3f66584f1 in QEventLoop::processEvents (this=this@entry=0x7ff3e2addd20, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007ff3f6658805 in QEventLoop::exec (this=this@entry=0x7ff3e2addd20, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007ff3f6556c39 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:538
#7  0x00007ff3f655939f in QThreadPrivate::start (arg=0xcc52a0) at thread/qthread_unix.cpp:349
#8  0x00007ff3f1fab0a5 in start_thread (arg=0x7ff3e2ade700) at pthread_create.c:309
#9  0x00007ff3f294f84d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7ff3f706b8c0 (LWP 9545)):
[KCrash Handler]
#6  0x00007ff3f288bd27 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#7  0x00007ff3f288d418 in __GI_abort () at abort.c:89
#8  0x00007ff3f2e9205d in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#9  0x00007ff3f2e8fed6 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#10 0x00007ff3f2e8ff21 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#11 0x00007ff3f2e90189 in __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#12 0x00007ff3f6658a1b in QEventLoop::exec (this=this@entry=0x7fff587f8d50, flags=...) at kernel/qeventloop.cpp:218
#13 0x00007ff3f665df67 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1225
#14 0x00007ff3f59e44dc in QApplication::exec () at kernel/qapplication.cpp:3828
#15 0x00007ff3f6b4b29c in Akonadi::ResourceBase::init (r=r@entry=0xb32d10) at ../../akonadi/resourcebase.cpp:579
#16 0x00000000004189fe in Akonadi::ResourceBase::init<ImapResource> (argc=<optimized out>, argv=<optimized out>) at /usr/include/akonadi/resourcebase.h:193
#17 0x00007ff3f2876ec5 in __libc_start_main (main=0x418300 <main(int, char**)>, argc=3, argv=0x7fff587f8ed8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff587f8ec8) at libc-start.c:287
#18 0x00000000004188a4 in _start ()

Possible duplicates by query: bug 341108, bug 341073, bug 340808, bug 340614, bug 339964.

Reported using DrKonqi
Comment 1 Myriam Schweingruber 2014-12-05 16:28:12 UTC
*** Bug 341528 has been marked as a duplicate of this bug. ***
Comment 2 Denis Kurz 2017-06-23 19:58:25 UTC
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.