This is a know which I am seeing only when running the script in Powershell/CMD. However when I run it in WSL, it runs fully. The "failed to get memory" message indicates the memory allocated has been used up. This issue can come up in Linux too. Only difference is I think how the memory is being managed when running inside WSL vs natively in Windows (via powershell)
Currently I don't have a fix for this issue. One way to bypass this would be to reduce the target directory scope. Let's say instead of running the tool on entire drive, run it on a specific folder of interest.
I am working on this at the moment. Will update if I can get a reasonable fix.
The 2 images are for the same D drive run at separate times in Powershell (1st image) and Ubuntu 22.04 WSL (2nd image).
This is a know which I am seeing only when running the script in Powershell/CMD. However when I run it in WSL, it runs fully. The "failed to get memory" message indicates the memory allocated has been used up. This issue can come up in Linux too. Only difference is I think how the memory is being managed when running inside WSL vs natively in Windows (via powershell)
Currently I don't have a fix for this issue. One way to bypass this would be to reduce the target directory scope. Let's say instead of running the tool on entire drive, run it on a specific folder of interest.
I am working on this at the moment. Will update if I can get a reasonable fix.
The 2 images are for the same D drive run at separate times in Powershell (1st image) and Ubuntu 22.04 WSL (2nd image).