View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000013 | FileSieve | Backend / Core | public | 2018-10-05 22:55 | 2018-10-05 22:55 |
| Reporter | BootBlock | Assigned To | BootBlock | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | assigned | Resolution | open | ||
| Summary | 0000013: Memory is not being released in a timely manner after processing | ||||
| Description | 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. | ||||
| Tags | No tags attached. | ||||
