Open awerty-noob opened 1 year ago
Same problem with my system when moving files from NVMe to HDD. CPU 1 core load is 100%. Where when I using mv
in shell is almost no load on CPU.
This is something that definitely needs fixing. Just not exactly sure how to go about this yet.
From my understanding: File operations are coded to be on separate threads. However, after the cut/copy operation is complete, the main thread is coded to try to join the file operation thread. This is to ensure these threads exit cleanly. However, for reason I'm not sure of, the join process takes a long time even though the thread is done.
Joshuto could froze when I copy some large file (above 1G). It would be fantastic if copy/paste/etc. can be handled by another process instead of main one, avoiding the possible stuck. As far as I know, lf file manager uses the backend/frontend to seperate the TUI with the I/O tasks. Does Joshuto has plan on this?