abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/bin/nepomukservicestub nepomukstrigiservice
comment: Nepomuk still crashes randomly when given to index a pretty large folder. It starts to index, hogs the cpu, does it for hours and crashes in the middle. After the crash it actually started everything over again, this time consuming much less resources and, what's more important, did not crash. Also, but this probably should be opened as another bug, Nepomuk reports having 6702 files in its index while I am storing only ca. 4000 files in folders I let him index. Probably it does not remove deleted files from indexes, but it is only my vague guess. While I see and buy the reasoning behind semantic desktop I am pretty sure that Nepomuk and friends is not the most reliable solution - it is not stable, sluggish, barely configurable (at least from UI perspective) and lacks proper end-user documentation (how do I rebuild an index?). Period. End of rant :-)
component: kdebase-runtime
crash_function: raise
executable: /usr/bin/nepomukservicestub
global_uuid: 8c50df396a345475e32a225ab1b0c9f40f6ad129
kernel: 2.6.32.16-141.fc12.i686.PAE
package: kdebase-runtime-4.4.5-1.fc12
rating: 4
reason: Process /usr/bin/nepomukservicestub was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)