<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugs.kde.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugs.kde.org/"
          
          maintainer="sysadmin@kde.org"
>

    <bug>
          <bug_id>403866</bug_id>
          
          <creation_ts>2019-02-02 16:18:29 +0000</creation_ts>
          <short_desc>Baloo uses too much memory</short_desc>
          <delta_ts>2019-05-14 09:22:42 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>3</classification_id>
          <classification>Frameworks and Libraries</classification>
          <product>frameworks-baloo</product>
          <component>general</component>
          <version>unspecified</version>
          <rep_platform>Other</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>DUPLICATE</resolution>
          <dup_id>394750</dup_id>
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>NOR</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          <everconfirmed>0</everconfirmed>
          <reporter>dag</reporter>
          <assigned_to>baloo-bugs-null</assigned_to>
          <cc>archmizuchi</cc>
    
    <cc>nate</cc>
          
          <cf_commitlink></cf_commitlink>
          <cf_versionfixedin></cf_versionfixedin>
          <cf_sentryurl></cf_sentryurl>
          <votes>0</votes>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>1835397</commentid>
    <comment_count>0</comment_count>
    <who name="">dag</who>
    <bug_when>2019-02-02 16:18:29 +0000</bug_when>
    <thetext>SUMMARY
The baloo file index seems to load the whole index file into memory and thus using huge amounts of memory and crippling the system

STEPS TO REPRODUCE
1. Ask baloo to index your files
2. Check the memory usage with top and note the RES use of baloo_file_indexer
   It seems to use a bot more than the size of the index file.
3. Kill it before it use up all of your memory (I killed it at 2.5GB RES usage)

OBSERVED RESULT
Too much memory used

EXPECTED RESULT
An indexer should use a lot less memory

SOFTWARE/OS VERSIONS

Linux/KDE Plasma: 5.42.0
(available in About System)
KDE Plasma Version: 5.12.2
KDE Frameworks Version: 5.42.0
Qt Version: 5.9.4

ADDITIONAL INFORMATION</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1856042</commentid>
    <comment_count>1</comment_count>
    <who name="Antoscha">archmizuchi</who>
    <bug_when>2019-05-14 09:15:52 +0000</bug_when>
    <thetext>This is a long lasting problem which reduce usability of KDE Plasma in the whole:

https://forum.antergos.com/topic/10830/baloo-memory-leak/10
https://www.reddit.com/r/kde/comments/7ch2kz/baloo_file_extractor_memory_leak_when_indexing/
https://bbs.archlinux.org/viewtopic.php?id=193169
https://forum.kde.org/viewtopic.php?t=121495
https://askubuntu.com/questions/1067499/baloo-file-extractor-in-ubuntu-18-04-lts-taking-up-a-lot-of-memory
https://forum.manjaro.org/t/baloo-file-extractor-running-wild-until-all-ram-is-used-and-computer-freezes/47545
https://forum.manjaro.org/t/baloo-file-uses-a-lot-of-ram/70079
https://www.reddit.com/r/kde/comments/723fzj/wtf_is_this_baloo_going_krazy/
https://forum.kde.org/viewtopic.php?t=141221

Tons of reports. The only solution is to disable baloo completely. May be it&apos;s worth to get rid of baloo, replace it in the Plasma environment with, say, GNOME Tracker until this bug fixed?</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>1856046</commentid>
    <comment_count>2</comment_count>
    <who name="Antoscha">archmizuchi</who>
    <bug_when>2019-05-14 09:22:42 +0000</bug_when>
    <thetext>

*** This bug has been marked as a duplicate of bug 394750 ***</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>