Summary: | kde-frameworks/baloo-5.18.0 - index is truncated back to 0 Bytes when it reaches 4096 MB | ||
---|---|---|---|
Product: | [Frameworks and Libraries] frameworks-baloo | Reporter: | David Kredba <kredba> |
Component: | general | Assignee: | Pinak Ahuja <pinak.ahuja> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | aspotashev, christoph, dennis.lissov, kdebugs, pinak.ahuja, stupor_scurvy343, theivorytower |
Priority: | NOR | ||
Version: | 5.18.0 | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
David Kredba
2016-02-05 18:26:06 UTC
free total used free shared buff/cache available Mem: 8169780 685688 5291612 10956 2192480 6712044 Swap: 8396796 955516 7441280 Linux srv5 4.4.1-gentoo #1 SMP PREEMPT Wed Feb 3 10:46:09 CET 2016 x86_64 Intel(R) Core(TM)2 Quad CPU Q9550 @ 2.83GHz GenuineIntel GNU/Linux There is the index file of size 4446269440 Bytes present in .local/share/baloo after I killed the baloo_file_extractor process and stopped baloo using balooctl stop. Same here, but I think it might be a 'balooctl status' display bug. It appears that the index is still there and searchable on my system: ~ $ balooctl status Baloo File Indexer is running Indexer state: Suspended Indexed 458732 / 506012 files Current size of index is 301.14 MiB ~/.local/share/baloo $ ls -al total 4502692 drwxr-xr-x 2 bjohnson users 4096 May 6 08:12 . drwx------ 46 bjohnson users 4096 May 5 14:57 .. -rw-r--r-- 1 bjohnson users 4610740224 May 6 08:16 index -rw-r--r-- 1 bjohnson users 8192 May 6 08:58 index-lock kinfocenter: Gentoo Linux KDE Plasma Version: 5.5.5 Qt Version: 5.5.1 Kernel Version: 4.4.6-gentoo OS Type: 64-bit Like David reports, once the index hits 4G 'balooctl status' reports 0MiB. However, search is still working on my system. The reason for this bug is that the size is stored in a "quint32" variable, and the maximum value a quint32 variable can take is 2^32, which equals 4096 MB. *** This bug has been marked as a duplicate of bug 364475 *** |