Open Radstor opened 1 year ago
@Radstor From what I understand, cpu hog only happens on some directories. Do these directories have an unusual setting for the file change/modification times? We had a similar issue on mounted directories which shows incorrect modification times in the future reported in #453 .
@gokcehan Thank you for your help. I tried lf running on a virtual machine (FreeBSD) on my MacBook (as I have no configuration files for lf on this system). I found that with Linux compatibility enabled when in the root directory if I move up and down on the folders/files, if I go over the /proc folder this occurs (high CPU usage) . If I disable Linux compatibility and restart then this does not happen as the /proc folder is empty. If I manually run "service ubuntu onestart" then the proc folder becomes populated (contents changes over time) and if I rerun lf and land on top of this /proc folder cpu usage goes high. This also happens on other folders, though I need to go deeper to replicate the issue. For example if I browse to /compat/ubuntu/proc or /compat/ubuntu/sys the same issue occurs (these folders are also empty when Linux compatibility is off and in that case the issue does not occur).
The issue I have experienced has been documented here:
https://forums.freebsd.org/threads/lf-file-manager-conflicting-with-linux-compatibility-layer-high-cpu-usage.88644/