Quote:
Originally posted by Unregistered
I've encountered what I think is a memory leak in 1.09. Physical memory declines down to 0 and then the program locks up. Nicely designed with the recovery/resume feature but it seems to have difficulties in the engine. |
In my original "excessive threads" report (for 2.09) XoloX consumed memory while indexing at a rate of aprox 1 MB per thread. (or maybe .5 as I think Sysmon is broken, reporting disk cache usage when there is none.) With 1 thread being created per (sub)directory shared, this can add up rather quickly. In 1.11 this is no longer a problem, probably because CRC checking as been taken out. Indexing the same 192 folders now uses ~3 MB of RAM.