I'm using now PCManFM 1.0.1 and have tested this again:
>> I'm using PCmanFM 0.9.9 and created a folder of 100.000 files with no
>> content. I created the files with a acript and PCmanFM was in this time
>> acttive in the related directory. The lot of changes forced to use 100% of
>> the cpu time of one core. PCmanFM crashed even after ~2 minutes (maybe
>> because of the lot of refreshes).
> The crash doesn't appear anymore but PCManFM needed ~2 minutes until it
> responded again.
There is no change in this. But I have noticed a bad behavior of the memory usage: It increased from 14 MB to 93 MB (which is not the problem). But after leaving the directory the memory usage decreased only from 93 MB to 90 MB.
>> After the creation was finished I opened PCmanFM again and switched to
>> the directory with the files. The loading time was very long and PCmanFM
>> used after this ~95 MB of memory.
> The loading time needs a few seconds and the memory usage increased to ~75
The memory usage doesn't increase anymore due to the (potential) memory leak (or whatever this is) from the last try. If I'm using a new process the memory usage will increase ~as said before. But leaving the directory again (or even closing the PCManFM window) will not free all the memory.
>> Using Ctrl + A to marking all files and pressing Del to show the delete
>> dialog needed a very long time too. But the deletion process was the
>> heaviest of all. Currently PCManFM uses over 10 minutes of cpu time of one
>> core just for deleting the files. But ls show me that not even one file is
>> in the 10 minutes deleted.
> Marking all files with Ctrl + A needs ~1-2 minutes. Pressing Del will
> prompt the deletion dialog instantly. The deletion process still needs a
> lot of cpu time. I have aborted it after ~15 minutes but this time over
> 6000 files were deleted.
Curiously pressing Ctrl + A will mark the files now instantly but opening the deletion prompt with Del will need 1-2 minutes. At least the deletion process has deleted now all 100000 files after ~6 minutes. But I have figured out that the window which shows the deletion process does not update the file which is currently processed.
Here is a short summary:
- On opening a directory with many files the memory usage will increase heavily without being freed.
- The deletion processing window does not update the file which is currently deleted.
- Having the directory opened which will create many files causes PCManFM to not respond for a short while.
- After marking a lot of files if a context menu is opened or the deletion prompt is directly called with Del PCManFM does not respond for a short while.
- The deletion process of many files needs some minutes.
Log in to post a comment.