[dolphin] [Bug 421042] New: Dolphin causes high (23%) CPU load, if gvfsd-fuse (encfs) is needed.

Alexander bugzilla_noreply at kde.org
Tue May 5 08:40:04 BST 2020


https://bugs.kde.org/show_bug.cgi?id=421042

            Bug ID: 421042
           Summary: Dolphin causes high (23%) CPU load, if gvfsd-fuse
                    (encfs) is needed.
           Product: dolphin
           Version: 20.04.0
          Platform: openSUSE RPMs
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: dolphin-bugs-null at kde.org
          Reporter: cookie170 at web.de
                CC: kfm-devel at kde.org
  Target Milestone: ---

SUMMARY

Dolphin causes high (23%) CPU load, if gvfsd-fuse (encfs) is needed.

openSUSE, Tumbleweed, up to date. 

/home is encrypted with LUKS. Inside /home is an encrypted folder. Encryption
by encfs.

STEPS TO REPRODUCE
1. open dolphin, go to /home/user/Dokumente/Encrypted while the encfs folder is
mounted. (encfs /home/user/Dokumente/.encryted /home/user/Dokumente/Encrypted )
2. open files, wait for some time
3. without an obvious reason, CPU load increases a lot and in TOP you'll see
that dolphin and gvfsd-fuse are the culprits. 

The CPU of about 23% load on this machine here won't go down; dolphin /
gvfsd-fuse will consume CPU load for hours. 

This bug exists at least since November 2019. I've been asking about this here:
https://forums.opensuse.org/showthread.php/538402-Dolphin-25-CPU-when-in-encrypted-(encfs)-file-system
w/o answer.

Operating System: openSUSE Tumbleweed 20200501
KDE Plasma Version: 5.18.4
KDE Frameworks Version: 5.69.0
Qt Version: 5.14.1
Kernel Version: 5.6.6-1-default
OS Type: 64-bit
Processors: 4 × Intel® Core™ i7-5600U CPU @ 2.60GHz
Memory: 7,5 GiB


OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION

-- 
You are receiving this mail because:
You are on the CC list for the bug.



More information about the kfm-devel mailing list