[frameworks-baloo] [Bug 379739] insane baloo_file (and plasmashell) 256 GB virtual memory size

https://bugs.kde.org/show_bug.cgi?id=379739 David Edmundson changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[frameworks-baloo] [Bug 379739] insane baloo_file (and plasmashell) 256 GB virtual memory size

https://bugs.kde.org/show_bug.cgi?id=379739 opensou...@candidminds.com changed: What|Removed |Added CC||opensou...@candidminds.com -- You

[frameworks-baloo] [Bug 379739] insane baloo_file (and plasmashell) 256 GB virtual memory size

https://bugs.kde.org/show_bug.cgi?id=379739 David Edmundson changed: What|Removed |Added CC|

[frameworks-baloo] [Bug 379739] insane baloo_file (and plasmashell) 256 GB virtual memory size

https://bugs.kde.org/show_bug.cgi?id=379739 --- Comment #4 from skierpage --- (In reply to skierpage from comment #3) > ... I can't immediately see why this is the cause of > baloo_file consuming 99% CPU. I guess it's more plausible my baloo/index > file is corrupt. I blew

[frameworks-baloo] [Bug 379739] insane baloo_file (and plasmashell) 256 GB virtual memory size

https://bugs.kde.org/show_bug.cgi?id=379739 --- Comment #3 from skierpage --- It seems this is intentional. In https://code.woboq.org/qt5/kf5/baloo/src/engine/database.cpp.html there's the comment * size limit for database == size limit of mmap * use 1 GB on

[frameworks-baloo] [Bug 379739] insane baloo_file (and plasmashell) 256 GB virtual memory size

https://bugs.kde.org/show_bug.cgi?id=379739 --- Comment #2 from skierpage --- (In reply to Rex Dieter from comment #1) > fyi, the VIRT table of memory you reference is not a good metric. RES+SHR > is a better measure of real usage. Sure. But it's not free to maintain

[frameworks-baloo] [Bug 379739] insane baloo_file (and plasmashell) 256 GB virtual memory size

https://bugs.kde.org/show_bug.cgi?id=379739 Rex Dieter changed: What|Removed |Added CC||rdie...@math.unl.edu ---