FileSieve 4

  • Status Assigned
  • Percent Complete
  • Task Type Bug Report (minor)
  • Category Backend / Core
  • Assigned To
    Joseph Cox
  • Operating System All
  • Severity Medium
  • Priority Low
  • Reported Version 4.00
  • Due in Version Undecided
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: FileSieve 4
Opened by Joseph Cox - 21 November 2016

FS#15 - Memory is not being released in a timely manner after processing

This may be down to the Windows API call FindNextFile() and file handles.

While it may not actually be a problem, I’d rather not use more memory the more files that are processed - even if memory usage goes up by just a few hundred megabytes for 4 to 5 million files, eliminating this memory usage would still be a win.

Joseph Cox commented on 21 November 2016 02:12 PM

Used the Visual Studio memory profiler and the memory usage is simply due to the sheer number of file objects (around 140 bytes each).

Maybe add a NoPrescan Get Files Mode to the Source Item Editor for users that have limited memory that need to scan files ranging in the tens of millions to billions - unlikely, but why have the limit when it can potentially be removed? Besides, some people might not care about the prescan and would just rather FileSieve immediately begin the sorting process.


Available keyboard shortcuts


Task Details

Task Editing