This issue is being investigated, at least here if not at MB.
The presumed issue is that Malwarebytes Anti-Ransomware, an experimental distinct offering from their main security product), injects hooks all over the system, resulting in what appears to be excessive CPU use by Process Lasso - though really it comes from their hooks.
We are tracking this down and I'm doing what I can. I have not heard from their developers yet, which may save me some time.
Until a resolution by MalwareBytes, or a work-around by Bitsum, I recommend:
First, if you aren't seeing massive CPU use, then you aren't affected! So, relax, congrats
. We've yet to reproduce it, so definitely not everyone is affected.
- Try disabling logging
- Try disabling Process Icons in the View Menu
- Set the ProcessLasso.exe GUI to start manually. There won't be a system tray icon, but the core engine (ProcessGovernor.exe) will keep running and managing processes in the background. You can then open the Process Lasso GUI when you need to check status or reconfigure the product.