Open ababak opened 7 years ago
That's not good. Is that on Windows?
Ooops, sorry. Windows 10 Pro
A big directory is network-based if that does matter (but relatively fast 10Gbit network).
Okay. Thanks!
Did you have a chance to find the reason for this bug? Please let me know if I could be of any help. Thanks.
I have not yet had time to look at it, sorry. Can you find out if the problem is caused by the large number of files (1500), or by the directory being network-based? For instance, you could check if other directories with many files are slow as well.
I've copied one of the network-based directories locally and it works more or less fine. So the problem appears after visiting network-based folders. What can fman do to these directories even after I switch to local drives?
fman's implementation for retrieving files is currently provided by a library it uses (Qt). Unfortunately, I have little insight into how this implementation works. I have just started to rewrite the implementation from scratch. This will allow me to find the root cause of problems like this one. And it will enable many other improvements like Zip file support. Unfortunately, it will require some time to implement. Sorry it's taking so long and please bear with me!
I have the same issue. fman lags for seconds when I enter a directory with 200+ items. It happens on external USB3.0 HDD and on Samba network drives as well. Obviously the issue is more severe on a 1GbE network share. Total commander does some magic here, it probably caches heavily.
The common magic in such cases is reading in background and displaying the first results as soon as possible.
The common magic in such cases is reading in background and displaying the first results as soon as possible.
That's what fman does since version 1.0.0 from a month ago. The problem now is rendering. I will be optimizing this throughout the coming months.
I´ve a very similar issue. Using Windows 10 on almost any action, be it changing directories, pressing a key or just giving focus to the window, it is lagging/freezing about 3 to sometimes 15 seconds. I am really desperate. I love the idea of the app. It is very minimalistic in its appearance and very powerful in its possibilities. I´d love to use it regularly, but right now I can´t. :-( I´m willing to pay more than the regular price for a license. I´d also invest my time to gather info or try workarounds. I already took a look into the core plugin, but it seems the bottleneck is not in there, but in the binaries. Any help / hint / ideas are greatly appreciated!
Do you have a very weak machine @FabBadDog? Or antivirus perhaps? 3+ seconds delay on every action does sound like a nightmare.
Hey Michael, thanks for the quick reply! I´ve a 1.9 ghz dual core with 8 Gb RAM. Should be sufficient, shouldn´t it? Anti-Virus is Windows Defender only. This is my daily dev-machine and everything apart from fman is running smoothly. It´s not so much a nightmare, I just can´t use it at all and I really would like to. I have been through a lot of file-managers (Midnight Commander, Directory Opus, XYplorer) over the years, but fman is a whole new approach and I am very sad I can´t use it.
With such a high-spec machine, that's really strange. Is it "just" opening directories that's slow? Or also opening dialogs, such as Ctrl+P or (say) F8?
It´s also other things. Startup, Opening Dialogs. But not necessarily always.
Hello Michael,
I am pretty sure now that it is related to running fman on a surface. I tested it on another machine with a similar setup (Windows 10) and it did not lag and the best thing is: I recently got a firmware update for the surface and gave it another try after noticing that other things have been sped up and voíla, lags are gone!
So I bought a license and I am happy for now. Thx for the support and keep up the good work!
Thank you Fabio! I'm happy to hear it works for you now. Will do.
After I visit a directory with about 1500 files, fman becomes unstable. Even if I go away to a different directory with 5-10 files, every directory change makes fman freeze. The only workaround is to restart fman. I can reproduce this bug every time.