Closed anylayer closed 1 month ago
This is a tricky one and I've found it is many times due to a race condition where the permissions on the memory changed while objection is using Memory.scan. Believe the error handling on this function is a bit better now though and it shouldn't crash the whole agent anymore, mostly mitigating the issue.
Describe the bug A clear and concise description of what the bug is.
To Reproduce Steps to reproduce the behavior:
Similar issues Please link the issues in this repository that is similar to yours.
326,#264
Environment (please complete the following information):