Weird second SA has no CPU

[smf007]

After updating to the latest DirMon, I noticed that my second spawned SA in not getting any CPU. It's on a uniprocessor, where I am spawning upto 2 SA as the queue requires. Each set to 49 resources out of a 100 total. Each instance is doing live detection. What it is doing now though is the first instance gets all left over CPU starving the 2nd. When the first finishes, the 2nd gets all the CPU even if another SA is spawned after the closing of the first.


Now, does that make any sense

[smf007]

After turning off logging in SA and setting throttling to on at 50%, magically it is back to "normal".

So.... forget about this for now. I'll run some tests after my mid terms.

[Jere_Jones]

I've found the cause of this. Apparently, running SA under a limited account interferes with SA deleting some of the old logs and it gets into an infinite loop trying to delete them.

It is fixed for the next version. Thanks!

Jere