Bug 332085

Summary:	Email Indexer crash - ChertWritableDatabase::add_document
Product:	[Frameworks and Libraries] Akonadi	Reporter:	Bruno Friedmann <bruno>
Component:	Indexer	Assignee:	kdepim bugs <pim-bugs-null>
Status:	RESOLVED UNMAINTAINED
Severity:	crash	CC:	chrigi_1, dvratil
Priority:	NOR	Keywords:	drkonqi
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Bruno Friedmann 2014-03-13 08:09:44 UTC

Application: akonadi_baloo_indexer (4.12)
KDE Platform Version: 4.12.80 (Compiled from sources)
Qt Version: 4.8.5
Operating System: Linux 3.13.6-1.g4727218-desktop x86_64
Distribution: "openSUSE 13.1 (Bottle) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
After getting the last postgresql patch for akonadi I reopened my kde session.

akonadi_baloo_indexing start its work, and then I got the crash

-- Backtrace:
Application: Akonadi Baloo Indexing Agent (akonadi_baloo_indexer), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#6  0x00007f547a510b43 in std::_Rb_tree_increment(std::_Rb_tree_node_base const*) () from /usr/lib64/libstdc++.so.6
#7  0x00007f547be1b165 in operator++ (this=<synthetic pointer>) at /usr/include/c++/4.8/bits/stl_tree.h:270
#8  ChertPostListTable::merge_changes (this=this@entry=0x23cacf8, mod_plists=std::map with 172052 elements, doclens=std::map with 10000 elements, freq_deltas=std::map with 172052 elements) at backends/chert/chert_postlist.cc:1206
#9  0x00007f547be08a35 in ChertWritableDatabase::flush_postlist_changes (this=this@entry=0x23cacc0) at backends/chert/chert_database.cc:1065
#10 0x00007f547be0a4e6 in ChertWritableDatabase::add_document_ (this=this@entry=0x23cacc0, did=did@entry=360600, document=...) at backends/chert/chert_database.cc:1228
#11 0x00007f547be0b606 in ChertWritableDatabase::replace_document (this=0x23cacc0, did=360600, document=...) at backends/chert/chert_database.cc:1457
#12 0x0000000000410a42 in EmailIndexer::index (this=0x2395d10, item=...) at /usr/src/debug/baloo-4.12.80/src/pim/agent/emailindexer.cpp:84
#13 0x000000000040b42d in BalooIndexingAgent::slotItemsRecevied (this=0x23412e0, items=...) at /usr/src/debug/baloo-4.12.80/src/pim/agent/agent.cpp:343
#14 0x00007f547d5cfd68 in QMetaObject::activate (sender=0x253e970, m=m@entry=0x7f547cd44fa0 <Akonadi::ItemFetchJob::staticMetaObject>, local_signal_index=local_signal_index@entry=0, argv=argv@entry=0x7fff7388d460) at kernel/qobject.cpp:3556
#15 0x00007f547c9df672 in Akonadi::ItemFetchJob::itemsReceived (this=<optimized out>, _t1=...) at /usr/src/debug/kdepimlibs-4.12.80/build/akonadi/moc_itemfetchjob.cpp:116
#16 0x00007f547c9e04d3 in timeout (this=<optimized out>) at /usr/src/debug/kdepimlibs-4.12.80/akonadi/itemfetchjob.cpp:74
#17 Akonadi::ItemFetchJob::qt_static_metacall (_o=0x378a1140, _c=37530872, _id=931747200, _a=0x0) at /usr/src/debug/kdepimlibs-4.12.80/build/akonadi/moc_itemfetchjob.cpp:67
#18 0x00007f547d5cfd68 in QMetaObject::activate (sender=0x253ec30, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3556
#19 0x00007f547d5d3f31 in QObject::event (this=0x253ec30, e=<optimized out>) at kernel/qobject.cpp:1165
#20 0x00007f547a97d9ec in QApplicationPrivate::notify_helper (this=this@entry=0x2166200, receiver=receiver@entry=0x253ec30, e=e@entry=0x7fff7388d9c0) at kernel/qapplication.cpp:4562
#21 0x00007f547a983fb0 in QApplication::notify (this=this@entry=0x7fff7388dcd0, receiver=receiver@entry=0x253ec30, e=e@entry=0x7fff7388d9c0) at kernel/qapplication.cpp:4348
#22 0x00007f547b91447a in KApplication::notify (this=0x7fff7388dcd0, receiver=0x253ec30, event=0x7fff7388d9c0) at /usr/src/debug/kdelibs-4.12.80/kdeui/kernel/kapplication.cpp:311
#23 0x00007f547d5bc0ad in QCoreApplication::notifyInternal (this=0x7fff7388dcd0, receiver=0x253ec30, event=0x7fff7388d9c0) at kernel/qcoreapplication.cpp:949
#24 0x00007f547d5eb83c in sendEvent (event=<optimized out>, receiver=<optimized out>) at kernel/qcoreapplication.h:231
#25 QTimerInfoList::activateTimers (this=0x2167470) at kernel/qeventdispatcher_unix.cpp:636
#26 0x00007f547d5e8b59 in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:186
#27 idleTimerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:233
#28 0x00007f54797ff316 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#29 0x00007f54797ff668 in ?? () from /usr/lib64/libglib-2.0.so.0
#30 0x00007f54797ff70c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#31 0x00007f547d5e8d55 in QEventDispatcherGlib::processEvents (this=0x212fa90, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#32 0x00007f547aa1aa76 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#33 0x00007f547d5bad0f in QEventLoop::processEvents (this=this@entry=0x7fff7388dc40, flags=...) at kernel/qeventloop.cpp:149
#34 0x00007f547d5bb005 in QEventLoop::exec (this=this@entry=0x7fff7388dc40, flags=...) at kernel/qeventloop.cpp:204
#35 0x00007f547d5c013b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1221
#36 0x00007f547a97c1ac in QApplication::exec () at kernel/qapplication.cpp:3823
#37 0x00007f547c937543 in Akonadi::AgentBase::init (r=r@entry=0x23412e0) at /usr/src/debug/kdepimlibs-4.12.80/akonadi/agentbase.cpp:853
#38 0x000000000040cb53 in Akonadi::AgentBase::init<BalooIndexingAgent> (argc=<optimized out>, argv=<optimized out>) at /usr/include/akonadi/agentbase.h:454
#39 0x00007f5479ef2be5 in __libc_start_main () from /lib64/libc.so.6
#40 0x00000000004087b5 in _start () at ../sysdeps/x86_64/start.S:122

Reported using DrKonqi

Comment 1 Denis Kurz 2016-09-24 20:36:00 UTC

This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.

Comment 2 Denis Kurz 2017-01-07 21:51:28 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.