You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Strippy can consume a large amount of memory when sanitising.
This is especially evident when processing collector (DT CAG) that is used as a RUM beacon. It is possible to consume 11-13 GB of memory and causing powershell to crash due to out of memory issue.
Version ~2.4 (To be confirmed.)
The text was updated successfully, but these errors were encountered:
How big was the source log filesystem?
Can you please run the script as normal with -log and make the output available to me?
It's a normal part of the powershell process to consume a significant amount of memory, That is required as part of the key finding and sanitisation process.
Strippy can consume a large amount of memory when sanitising.
This is especially evident when processing collector (DT CAG) that is used as a RUM beacon. It is possible to consume 11-13 GB of memory and causing powershell to crash due to out of memory issue.
Version ~2.4 (To be confirmed.)
The text was updated successfully, but these errors were encountered: