Bug 355924 - Baloo crash - Baloo::IdFilenameDB::put - mdb_page_dirty
Summary: Baloo crash - Baloo::IdFilenameDB::put - mdb_page_dirty
Status: RESOLVED DUPLICATE of bug 362222
Alias: None
Product: frameworks-baloo
Classification: Frameworks and Libraries
Component: Baloo File Daemon (show other bugs)
Version: 5.15.0
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Pinak Ahuja
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2015-11-26 08:49 UTC by Boilley Adrien
Modified: 2016-09-11 21:04 UTC (History)
5 users (show)

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 Boilley Adrien 2015-11-26 08:49:34 UTC
Application: baloo_file (5.15.0)

Qt Version: 5.4.2
Operating System: Linux 4.2.0-18-generic x86_64
Distribution: Ubuntu 15.10

-- Information about the crash:
- What I was doing when the application crashed:
I don't know why : baloo (what is it?) reported a crash just when i created a folder on desktop from a konsole.

I use Kubuntu 15.10 / 64b.

Thank,
Adrien.

-- Backtrace:
Application: Baloo File Indexing Daemon (baloo_file), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f30e2b68800 (LWP 1079))]

Thread 2 (Thread 0x7f2f97d08700 (LWP 5039)):
[KCrash Handler]
#6  0x00007f30e0bef267 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55
#7  0x00007f30e0bf0eca in __GI_abort () at abort.c:89
#8  0x00007f30df4041b2 in mdb_assert_fail (env=0xd26250, expr_txt=expr_txt@entry=0x7f30df4101cf "rc == 0", func=func@entry=0x7f30df410ac5 <__FUNCTION__.6980> "mdb_page_dirty", line=line@entry=1945, file=0x7f30df4101b0 "mdb.c") at mdb.c:1369
#9  0x00007f30df4045f5 in mdb_page_dirty (txn=0xdfcd60, mp=<optimized out>) at mdb.c:1945
#10 0x00007f30df4057cb in mdb_page_alloc (num=num@entry=1, mp=mp@entry=0x7f2f97d06f78, mc=0x7f2f97d074b0) at mdb.c:2126
#11 0x00007f30df405a29 in mdb_page_touch (mc=mc@entry=0x7f2f97d074b0) at mdb.c:2244
#12 0x00007f30df407664 in mdb_cursor_touch (mc=mc@entry=0x7f2f97d074b0) at mdb.c:6086
#13 0x00007f30df40a27a in mdb_cursor_put (mc=0x7f2f97d074b0, key=0x7f2f97d07890, data=0x7f2f97d078a0, flags=<optimized out>) at mdb.c:6221
#14 0x00007f30df40cb29 in mdb_put (txn=<optimized out>, dbi=<optimized out>, key=key@entry=0x7f2f97d07890, data=data@entry=0x7f2f97d078a0, flags=flags@entry=0) at mdb.c:8395
#15 0x00007f30e1d61219 in Baloo::IdFilenameDB::put (this=this@entry=0x7f2f97d07910, docId=docId@entry=61363357399123974, path=...) at ../../../src/engine/idfilenamedb.cpp:75
#16 0x00007f30e1d5cc10 in Baloo::DocumentUrlDB::add (this=this@entry=0x7f2f97d07bd0, id=id@entry=61363357399123974, parentId=parentId@entry=3377725490333702, name=...) at ../../../src/engine/documenturldb.cpp:135
#17 0x00007f30e1d5cfa6 in Baloo::DocumentUrlDB::put (this=this@entry=0x7f2f97d07bd0, docId=docId@entry=61363357399123974, url=...) at ../../../src/engine/documenturldb.cpp:69
#18 0x00007f30e1d73f2a in Baloo::WriteTransaction::addDocument (this=0x7f2f90003870, doc=...) at ../../../src/engine/writetransaction.cpp:56
#19 0x00007f30e1d6db79 in Baloo::Transaction::addDocument (this=this@entry=0x7f2f97d07c90, doc=...) at ../../../src/engine/transaction.cpp:235
#20 0x000000000041bcff in Baloo::NewFileIndexer::run (this=0xeca500) at ../../../src/file/newfileindexer.cpp:72
#21 0x00007f30e16ace73 in QThreadPoolThread::run (this=0xe23070) at thread/qthreadpool.cpp:93
#22 0x00007f30e16b02be in QThreadPrivate::start (arg=0xe23070) at thread/qthread_unix.cpp:337
#23 0x00007f30e03226aa in start_thread (arg=0x7f2f97d08700) at pthread_create.c:333
#24 0x00007f30e0cc0eed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f30e2b68800 (LWP 1079)):
#0  0x00007f30e0cb149d in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007f30ddee64e0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f30ddea2cd4 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f30ddea3190 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f30ddea32fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f30e18e729b in QEventDispatcherGlib::processEvents (this=0xd14010, flags=...) at kernel/qeventdispatcher_glib.cpp:420
#6  0x00007f30e188d75a in QEventLoop::exec (this=this@entry=0x7ffc47daebd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#7  0x00007f30e18952cc in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1188
#8  0x0000000000415aec in main (argc=1, argv=<optimized out>) at ../../../src/file/main.cpp:88

Reported using DrKonqi
Comment 1 Braden Anderson 2015-12-10 23:08:02 UTC
I get the same thing occasionally. It happened around the time I started up Grunt just now. Here's my backtrace:

Application: Baloo File Indexing Daemon (baloo_file), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fea90846800 (LWP 1700))]

Thread 2 (Thread 0x7fe94fe21700 (LWP 3610)):
[KCrash Handler]
#6  0x00007fea9a449267 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:55
#7  0x00007fea9a44aeca in __GI_abort () at abort.c:89
#8  0x00007fea98a5a1b2 in mdb_assert_fail (env=0x1cde170, expr_txt=expr_txt@entry=0x7fea98a661cf "rc == 0", func=func@entry=0x7fea98a66ac5 <__FUNCTION__.6980> "mdb_page_dirty", line=line@entry=1945, file=0x7fea98a661b0 "mdb.c") at mdb.c:1369
#9  0x00007fea98a5a5f5 in mdb_page_dirty (txn=0x1cee9d0, mp=<optimized out>) at mdb.c:1945
#10 0x00007fea98a5b7cb in mdb_page_alloc (num=num@entry=1, mp=mp@entry=0x7fe94fe20460, mc=0x7fe94fe20980) at mdb.c:2126
#11 0x00007fea98a5d6b4 in mdb_page_new (mc=mc@entry=0x7fe94fe20980, flags=flags@entry=1, num=num@entry=1, mp=mp@entry=0x7fe94fe20528) at mdb.c:6711
#12 0x00007fea98a5de4f in mdb_page_split (mc=mc@entry=0x7fe94fe20980, newkey=newkey@entry=0x7fe94fe208d0, newdata=0x7fe94fe208e0, newpgno=newpgno@entry=18446744073709551615, nflags=nflags@entry=65536) at mdb.c:8021
#13 0x00007fea98a60533 in mdb_cursor_put (mc=0x7fe94fe20980, key=0x7fe94fe208d0, data=0x7fe94fe208e0, flags=<optimized out>) at mdb.c:6495
#14 0x00007fea98a61f15 in mdb_freelist_save (txn=0x1cee9d0) at mdb.c:3006
#15 mdb_txn_commit (txn=0x1cee9d0) at mdb.c:3405
#16 0x00007fea9b5c7c00 in Baloo::Transaction::commit (this=this@entry=0x7fe94fe20bf0) at ../../../src/engine/transaction.cpp:275
#17 0x000000000041d255 in Baloo::ModifiedFileIndexer::run (this=0x219a7f0) at ../../../src/file/modifiedfileindexer.cpp:103
#18 0x00007fea9af06e73 in QThreadPoolThread::run (this=0x1e4c9c0) at thread/qthreadpool.cpp:93
#19 0x00007fea9af0a2be in QThreadPrivate::start (arg=0x1e4c9c0) at thread/qthread_unix.cpp:337
#20 0x00007fea9a1fd6aa in start_thread (arg=0x7fe94fe21700) at pthread_create.c:333
#21 0x00007fea9a51aeed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7fea90846800 (LWP 1700)):
#0  0x00007fea9a50b49d in read () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007fea93701f75 in ?? () from /usr/lib/nvidia-352/tls/libnvidia-tls.so.352.63
#2  0x00007fea977404e0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fea976fccd4 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007fea976fd190 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007fea976fd2fc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x00007fea9b14127f in QEventDispatcherGlib::processEvents (this=0x1c2cac0, flags=...) at kernel/qeventdispatcher_glib.cpp:418
#7  0x00007fea9b0e775a in QEventLoop::exec (this=this@entry=0x7ffee0796a00, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204
#8  0x00007fea9b0ef2cc in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1188
#9  0x0000000000415aec in main (argc=1, argv=<optimized out>) at ../../../src/file/main.cpp:88
Comment 2 Larry 2016-04-25 21:08:37 UTC
I have it as well.  Found it while monitoring .xsession-errors trying to troubleshoot other problems in F23.
Comment 3 Christoph Cullmann 2016-09-11 21:02:19 UTC
Guess thats a follow up of corruption of the vector because of wrong insert.

*** This bug has been marked as a duplicate of bug 367991 ***
Comment 4 Christoph Cullmann 2016-09-11 21:04:10 UTC
Wrong, that would be IdTreeDb
Comment 5 Christoph Cullmann 2016-09-11 21:04:57 UTC
Use right bug, for idfilenamedb, still open.

*** This bug has been marked as a duplicate of bug 362222 ***