Slowdown after repeated enter directory move operations.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 275
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
Scenario:
Fresh copy of fman (downloaded 2025-04-05) running on latest Windows.
In one directory I have several hundreds of sub-directories containing one file each. I need to move the file from each of the sub-directories to another folder.
Procedure:
For each folder I repeat the following procedure:
- Press enter to open the folder.
- Press F6 to move the containing file (already highlighted).
- Press return to confirm moving.
- Press backspace to go back to start directory.
- Press arrow down to step down to next folder.
Repeat a few dozen times. This can be done in less than 2 seconds per entry once muscle memory kicks in. Don't know if speed of operation matters.
Result
After a few dozen of entries you will notice a clear slowdown in step 4. It starts to take several seconds for the main directory to render and in that time you can not do anything. The filenames comes up immediately, but the icons and additional file info takes time. The problem gets worse the more you continue the above procedure.
Restarting fman brings everything back to normal (blazingly fast), but the scenario repeats every time.
On an end note I just want to say thanks for developing fman and bringing the power of NC to all major platforms. I use all three platforms on a regular basis and having the same tool on all machines makes my life easier. Keep up the good work. :)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the repeated enter, F6, confirm, backspace, and arrow-down procedure on Windows with many subdirectories. Observe the delay while the main directory renders, especially icons and additional file information, and compare behavior before and after restarting fman. The issue names no files, tests, or entry points, so the affected code must first be located.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100