baloo_file_extractor crashed with SIGSEGV in Xapian::Database::get_document()

[Stephan Richter]

It runs in the background, uses a lot of CPU for a while then crashes. The error seems unrelated to the other crash reported on 4/3/2014.

I am running 14.04 beta.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: baloo 4:4.12.97-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8
Uname: Linux 3.13.0-23-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.14.1-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: KDE
Date: Sun Apr 6 16:53:21 2014
ExecutablePath: /usr/bin/baloo_file_extractor
InstallationDate: Installed on 2013-05-08 (333 days ago)
InstallationMedia: Kubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
ProcCmdline: /usr/bin/baloo_file_extractor 8408 8407 8406 8404 8403 8402 8401 8399 8398 8397 8396 8394 8393 8391 8390 8389 8388 8386 8384 8383 8382 8381 8379 8378 8377 8376 8375 8374 8373 8372 8369 8368 8366 8365 8363 8362 8361 8360 8359 8358
SegvAnalysis:
 Segfault happened at: 0x7f3b569e9e78 <_ZNK6Xapian8Database12get_documentEj+8>: mov 0x10(%rsi),%rcx
 PC (0x7f3b569e9e78) ok
 source "0x10(%rsi)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%rcx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: baloo
Stacktrace:
 #0 0x00007f3b569e9e78 in Xapian::Database::get_document(unsigned int) const () from /usr/lib/libxapian.so.22
 No symbol table info available.
 #1 0x0000000000408f2e in _start ()
 No symbol table info available.
StacktraceTop:
 Xapian::Database::get_document(unsigned int) const () from /usr/lib/libxapian.so.22
 _start ()
Title: baloo_file_extractor crashed with SIGSEGV in Xapian::Database::get_document()
UpgradeStatus: Upgraded to trusty on 2014-04-06 (0 days ago)
UserGroups: adm cdrom dip lp lpadmin plugdev sambashare sudo vboxusers

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1301742, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.