Bug 335715 - crash on trying to search mail in KMail
Summary: crash on trying to search mail in KMail
Status: RESOLVED FIXED
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2014-06-02 20:13 UTC by Martin Steigerwald
Modified: 2014-06-26 11:49 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 4.13.3


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Steigerwald 2014-06-02 20:13:29 UTC
Application: kmail (4.14 pre)
KDE Platform Version: 4.13.1 (Compiled from sources)
Qt Version: 4.8.6
Operating System: Linux 3.15.0-rc7-tp520 x86_64
Distribution: Debian GNU/Linux unstable (sid)

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

I searched for a mail in sent folder.

Selected sent folder, typed a search phrase, a word into the quick search bar and then it crashed.

With mails stored in maildir resource.

Self compiled akonadi, baloo, baloo-widgets, kdepim-runtime, kdepimlibs and kdepim as of today. Rest from Debian Qt/KDE 4.12/4.13 packages.

Thanks,
Martin

The crash can be reproduced every time.

-- Backtrace:
Application: KMail (kmail), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fae8d8c3900 (LWP 8162))]

Thread 3 (Thread 0x7fae680aa700 (LWP 8167)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007fae806017d2 in WTF::TCMalloc_PageHeap::scavengerThread (this=<optimized out>) at wtf/FastMalloc.cpp:2499
#2  0x00007fae80601809 in WTF::TCMalloc_PageHeap::runScavengerThread (context=<optimized out>) at wtf/FastMalloc.cpp:1622
#3  0x00007fae85bb3062 in start_thread (arg=0x7fae680aa700) at pthread_create.c:312
#4  0x00007fae87581c1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7fae677a9700 (LWP 8168)):
#0  0x00007fae8757690d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fae7beb7fe4 in g_main_context_poll (priority=2147483647, n_fds=1, fds=0x7fae60003280, timeout=663, context=0x7fae600009a0) at /tmp/buildd/glib2.0-2.40.0/./glib/gmain.c:4028
#2  g_main_context_iterate (context=context@entry=0x7fae600009a0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at /tmp/buildd/glib2.0-2.40.0/./glib/gmain.c:3729
#3  0x00007fae7beb80ec in g_main_context_iteration (context=0x7fae600009a0, may_block=1) at /tmp/buildd/glib2.0-2.40.0/./glib/gmain.c:3795
#4  0x00007fae88214676 in QEventDispatcherGlib::processEvents (this=0x7fae600008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:427
#5  0x00007fae881e5fef in QEventLoop::processEvents (this=this@entry=0x7fae677a8ce0, flags=...) at kernel/qeventloop.cpp:149
#6  0x00007fae881e62e5 in QEventLoop::exec (this=this@entry=0x7fae677a8ce0, flags=...) at kernel/qeventloop.cpp:204
#7  0x00007fae880e2bef in QThread::exec (this=<optimized out>) at thread/qthread.cpp:538
#8  0x00007fae880e52bf in QThreadPrivate::start (arg=0x187dc20) at thread/qthread_unix.cpp:349
#9  0x00007fae85bb3062 in start_thread (arg=0x7fae677a9700) at pthread_create.c:312
#10 0x00007fae87581c1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7fae8d8c3900 (LWP 8162)):
[KCrash Handler]
#6  0x00007fae874d13a9 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#7  0x00007fae874d44c8 in __GI_abort () at abort.c:89
#8  0x00007fae87dbfd65 in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#9  0x00007fae87dbddd6 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#10 0x00007fae87dbde21 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#11 0x00007fae87dbe089 in __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#12 0x00007fae881e64d6 in QEventLoop::exec (this=this@entry=0x7fff43dd8dc0, flags=...) at kernel/qeventloop.cpp:218
#13 0x00007fae881ebab9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1225
#14 0x00007fae88be7e8c in QApplication::exec () at kernel/qapplication.cpp:3828
#15 0x0000000000402e18 in main (argc=<optimized out>, argv=<optimized out>) at /home/martin/KDE/Dev/kdepim/kmail/main.cpp:146

Possible duplicates by query: bug 334929, bug 333879, bug 333358, bug 333332, bug 333327.

Reported using DrKonqi
Comment 1 Laurent Montel 2014-06-19 07:05:19 UTC
I think that it's an exception in baloo.
I caught some exception in baloo in 4.13.3
I hope that it will fix for you
Comment 2 Martin Steigerwald 2014-06-19 10:05:03 UTC
Is fix in source yet? I recompiled baloo, kdepimlibs, kdepim-runtime and kdepim in that order yesterday from recent git master and it still crashes. Do I need anything else? Thanks, Martin
Comment 3 Martin Steigerwald 2014-06-22 13:28:37 UTC
This crash has gone after I removed all Baloo data after:

[Akonadi] [Bug 336581] New: accidental database loss causes Akonadi / KMail breaks correct folder assignments

[Akonadi] [Bug 336582] New: Sudden write interruption during akonadictl vacuum causes database corruption

Thus I suspect some Baloo data was corrupted (for whatever reason).
Comment 4 Laurent Montel 2014-06-26 11:49:10 UTC
I added more "catch exception" I hope that it will ok for 4.13.3
I can't reproduce so I can't tell you that it's fixed or not.

Reopen it if necessary.