Bug 402266 - Baloo_file_extractor Crashes in KFileMetaData::TagLibExtractor::extract()
Summary: Baloo_file_extractor Crashes in KFileMetaData::TagLibExtractor::extract()
Status: RESOLVED FIXED
Alias: None
Product: frameworks-kfilemetadata
Classification: Frameworks and Libraries
Component: general (other bugs)
Version First Reported In: 5.53.0
Platform: Neon Linux
: NOR crash
Target Milestone: ---
Assignee: Pinak Ahuja
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2018-12-17 23:34 UTC by Bradley Ridnour
Modified: 2019-01-07 19:42 UTC (History)
4 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bradley Ridnour 2018-12-17 23:34:44 UTC
Application: baloo_file_extractor (5.53.0)

Qt Version: 5.11.2
Frameworks Version: 5.53.0
Operating System: Linux 4.15.0-42-generic x86_64
Distribution: KDE neon User Edition 5.14

-- Information about the crash:
I get this error whenever I log into KDE. This includes after logout and login, reboot and login, or shutdown and login.

The crash can be reproduced every time.

-- Backtrace:
Application: Baloo File Extractor (baloo_file_extractor), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fcace5e4c80 (LWP 31819))]

Thread 3 (Thread 0x7fcaa726b700 (LWP 31838)):
#0  0x00007fcacb166bf9 in __GI___poll (fds=0x7fcaa001a970, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x00007fcac7833539 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007fcac783364c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007fcacbaa104b in QEventDispatcherGlib::processEvents (this=0x7fcaa0000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#4  0x00007fcacba4530a in QEventLoop::exec (this=this@entry=0x7fcaa726ad70, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214
#5  0x00007fcacb870bba in QThread::exec (this=<optimized out>) at thread/qthread.cpp:525
#6  0x00007fcacd3c6e45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7  0x00007fcacb87badb in QThreadPrivate::start (arg=0x7fcacd63ed60) at thread/qthread_unix.cpp:367
#8  0x00007fcac9d6d6db in start_thread (arg=0x7fcaa726b700) at pthread_create.c:463
#9  0x00007fcacb17388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 2 (Thread 0x7fcabfff3700 (LWP 31821)):
#0  0x00007fcacb166bf9 in __GI___poll (fds=0x7fcabfff2ca8, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x00007fcac73c2747 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x00007fcac73c436a in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x00007fcac2fb3ed9 in QXcbEventReader::run (this=0x555c5eb61630) at qxcbconnection.cpp:1391
#4  0x00007fcacb87badb in QThreadPrivate::start (arg=0x555c5eb61630) at thread/qthread_unix.cpp:367
#5  0x00007fcac9d6d6db in start_thread (arg=0x7fcabfff3700) at pthread_create.c:463
#6  0x00007fcacb17388f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 1 (Thread 0x7fcace5e4c80 (LWP 31819)):
[KCrash Handler]
#6  0x00007fcaa768404b in KFileMetaData::TagLibExtractor::extract (this=<optimized out>, result=0x7ffc841ac2d0) at ./src/extractors/taglibextractor.cpp:851
#7  0x0000555c5d3f041b in Baloo::App::index (this=this@entry=0x7ffc841aca20, tr=0x555c5ebe7300, url=..., id=id@entry=59120224829491) at ./src/file/extractor/app.cpp:191
#8  0x0000555c5d3f0d5e in Baloo::App::processNextFile (this=0x7ffc841aca20) at ./src/file/extractor/app.cpp:111
#9  0x00007fcacba82ef4 in QtPrivate::QSlotObjectBase::call (a=0x7ffc841ac430, r=<optimized out>, this=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:376
#10 QSingleShotTimer::timerEvent (this=0x555c5ec7c500) at kernel/qtimer.cpp:318
#11 0x00007fcacba76b9b in QObject::event (this=0x555c5ec7c500, e=<optimized out>) at kernel/qobject.cpp:1273
#12 0x00007fcacc7d3e1c in QApplicationPrivate::notify_helper (this=this@entry=0x555c5eb4f980, receiver=receiver@entry=0x555c5ec7c500, e=e@entry=0x7ffc841ac700) at kernel/qapplication.cpp:3727
#13 0x00007fcacc7db3ef in QApplication::notify (this=0x7ffc841ac9f0, receiver=0x555c5ec7c500, e=0x7ffc841ac700) at kernel/qapplication.cpp:3486
#14 0x00007fcacba46fe8 in QCoreApplication::notifyInternal2 (receiver=0x555c5ec7c500, event=event@entry=0x7ffc841ac700) at kernel/qcoreapplication.cpp:1048
#15 0x00007fcacbaa04be in QCoreApplication::sendEvent (event=0x7ffc841ac700, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:234
#16 QTimerInfoList::activateTimers (this=0x555c5eb941b0) at kernel/qtimerinfo_unix.cpp:643
#17 0x00007fcacbaa0cb9 in timerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:182
#18 idleTimerSourceDispatch (source=<optimized out>) at kernel/qeventdispatcher_glib.cpp:229
#19 0x00007fcac7833387 in g_main_context_dispatch () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007fcac78335c0 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x00007fcac783364c in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x00007fcacbaa102f in QEventDispatcherGlib::processEvents (this=0x555c5eb91490, flags=...) at kernel/qeventdispatcher_glib.cpp:422
#23 0x00007fcac303f761 in QPAEventDispatcherGlib::processEvents (this=0x555c5eb91490, flags=...) at qeventdispatcher_glib.cpp:69
#24 0x00007fcacba4530a in QEventLoop::exec (this=this@entry=0x7ffc841ac970, flags=..., flags@entry=...) at kernel/qeventloop.cpp:214
#25 0x00007fcacba4e4d0 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1336
#26 0x0000555c5d3ef3f4 in main (argc=<optimized out>, argv=0x7ffc841acc48) at ./src/file/extractor/main.cpp:60

Reported using DrKonqi
Comment 1 Nate Graham 2018-12-26 23:37:08 UTC
There is probably a specific file causing the extractor to crash.
Comment 2 Alexander Stippich 2019-01-05 16:22:30 UTC
Can you determine the file which causes the crash using balooctl monitor? 
It should be a wma file.
Comment 3 Bradley Ridnour 2019-01-05 19:23:09 UTC
(In reply to Alexander Stippich from comment #2)
> Can you determine the file which causes the crash using balooctl monitor? 
> It should be a wma file.

Unfortunately no. The problem recently fixed itself during a system upgrade.