Bug 339739 - kmail/kontact 4.14.1 crashes when compacting a folder with ghost items
Summary: kmail/kontact 4.14.1 crashes when compacting a folder with ghost items
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kontact
Classification: Applications
Component: mail (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-07 06:14 UTC by Sven Eden
Modified: 2018-02-01 09:55 UTC (History)
0 users

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 Sven Eden 2014-10-07 06:14:08 UTC
Application: kontact (4.14.1)
KDE Platform Version: 4.14.1 (Compiled from sources)
Qt Version: 4.8.5
Operating System: Linux 3.15.10-geek x86_64
Distribution (Platform): Gentoo Packages

-- Information about the crash:
For a while now I keep getting error messages from our IMAP server:

Save failed, server response: A000008 BAD Command Argument Error. 12

I tracked it down to a ghost item in my outbox. The Folder is empty when opened
and there is nothing in the folder on my hard disk either.


- What I was doing when the application crashed:
To get rid of this item I tried to archive (compact?) the folder. Kontact crashed at once.

- Unusual behavior I noticed:
Persistent ghost item in the outbox folder.

-- Backtrace:
Application: Kontact (kontact), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f6be1f9e900 (LWP 30005))]

Thread 4 (Thread 0x7f6bc7003700 (LWP 30006)):
#0  pthread_cond_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007f6bdcda1622 in ?? () from /usr/lib64/qt4/libQtWebKit.so.4
#2  0x00007f6bdcda1659 in ?? () from /usr/lib64/qt4/libQtWebKit.so.4
#3  0x00007f6bd9d47083 in start_thread (arg=0x7f6bc7003700) at pthread_create.c:309
#4  0x00007f6bdf4ee36d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 3 (Thread 0x7f6bc6702700 (LWP 30007)):
#0  0x00007f6bdf4e4c8d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007f6bd8f08a7e in g_main_context_poll (priority=<optimized out>, n_fds=1, fds=0x7f6bc0003290, timeout=-1, context=0x7f6bc00009a0) at /home/portage/dev-libs/glib-2.40.0-r1/work/glib-2.40.0/glib/gmain.c:4028
#2  g_main_context_iterate (context=context@entry=0x7f6bc00009a0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at /home/portage/dev-libs/glib-2.40.0-r1/work/glib-2.40.0/glib/gmain.c:3729
#3  0x00007f6bd8f08b8c in g_main_context_iteration (context=0x7f6bc00009a0, may_block=1) at /home/portage/dev-libs/glib-2.40.0-r1/work/glib-2.40.0/glib/gmain.c:3795
#4  0x00007f6be0923ebe in QEventDispatcherGlib::processEvents (this=0x7f6bc00008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:452
#5  0x00007f6be08f43c8 in QEventLoop::processEvents (this=this@entry=0x7f6bc6701c90, flags=...) at kernel/qeventloop.cpp:149
#6  0x00007f6be08f46dd in QEventLoop::exec (this=this@entry=0x7f6bc6701c90, flags=...) at kernel/qeventloop.cpp:204
#7  0x00007f6be07e7fb8 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:536
#8  0x00007f6be07ea73b in QThreadPrivate::start (arg=0x1306850) at thread/qthread_unix.cpp:338
#9  0x00007f6bd9d47083 in start_thread (arg=0x7f6bc6702700) at pthread_create.c:309
#10 0x00007f6bdf4ee36d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7f6b70b10700 (LWP 30849)):
#0  pthread_cond_wait () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007f6b7daecedb in QTWTF::TCMalloc_PageHeap::scavengerThread (this=0x7f6b7dde8280 <QTWTF::pageheap_memory>) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359
#2  0x00007f6b7daecf29 in QTWTF::TCMalloc_PageHeap::runScavengerThread (context=<optimized out>) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464
#3  0x00007f6bd9d47083 in start_thread (arg=0x7f6b70b10700) at pthread_create.c:309
#4  0x00007f6bdf4ee36d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7f6be1f9e900 (LWP 30005)):
[KCrash Handler]
#6  0x00007f6bdf43b2a9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#7  0x00007f6bdf43c5e8 in __GI_abort () at abort.c:89
#8  0x00007f6bdf809745 in __gnu_cxx::__verbose_terminate_handler () at /home/portage/sys-devel/gcc-4.8.3/work/gcc-4.8.3/libstdc++-v3/libsupc++/vterminate.cc:95
#9  0x00007f6bdf807876 in __cxxabiv1::__terminate (handler=<optimized out>) at /home/portage/sys-devel/gcc-4.8.3/work/gcc-4.8.3/libstdc++-v3/libsupc++/eh_terminate.cc:38
#10 0x00007f6bdf8078a3 in std::terminate () at /home/portage/sys-devel/gcc-4.8.3/work/gcc-4.8.3/libstdc++-v3/libsupc++/eh_terminate.cc:48
#11 0x00007f6bdf807b16 in __cxxabiv1::__cxa_rethrow () at /home/portage/sys-devel/gcc-4.8.3/work/gcc-4.8.3/libstdc++-v3/libsupc++/eh_throw.cc:125
#12 0x00007f6be08f48d9 in QEventLoop::exec (this=this@entry=0x7fff4b4933e0, flags=...) at kernel/qeventloop.cpp:218
#13 0x00007f6be08f9b99 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1221
#14 0x00007f6bdfc7626c in QApplication::exec () at kernel/qapplication.cpp:3823
#15 0x00000000004036b3 in main (argc=1, argv=0x7fff4b493668) at /home/portage/kde-base/kontact-4.14.1/work/kontact-4.14.1/kontact/src/main.cpp:219

Possible duplicates by query: bug 336361, bug 334929, bug 334556, bug 334087, bug 333735.

An https://bugs.kde.org/ berichten

Reproducible: Always
Comment 1 Denis Kurz 2017-06-23 19:37:50 UTC
This bug has never been confirmed for a Kontact 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.
Comment 2 Denis Kurz 2018-02-01 09:55:49 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.