« Last post by chris635 on June 24, 2016, 07:01:28 PM »
I am going to reinstall everything and if it happens, I'll take some screen shots for ya...good?
please correct me if I'm wrong. It is that if MBARW is present, the CPU cycles used by ProcessLasso.exe varies dramatically on the same hardware, right?
I long ago optimized the rate of process handle opening to fix a previous interoperability issue with some security software that hooked all process opens to evaluate them. This reduced the rate of handle re-opens (which are normally rapid anyway, when not intercepted) by several orders of magnitude. Once per process instance, instead of once per second per process instance.When I said memory/handles I was talking in general, not specific to PL, but some issue when all these products ar run.
Somehow, this old report, despite long being fixed, caused an MB mod to conclude, after seeing a few process opens (which Process Lasso does since it manages processes!), that the fault must be with Process Lasso, despite no such problem occurring without the presence of MBARW!
Then the thread was closed. So, that's that. I can guarantee you that I spend extraordinary efforts to make Process Lasso as optimal as possible, but can't speak for whatever security software hooks do when they start blocking requests for inspection. We don't have any reason to suspect that process handle open frequency is the problem here, but it was taken as such, and the thread immediately closed without evidence of such.
I'll try to help them when I can, but there is only so much I can do, and at that point I'll just remove their product from my system, problem solved.