There are now three things ProBalance can change:
1. Process Priority
2. Process "Efficiency" flag
3. Process CPU affinity
From trial and error, it seems that 1 and 2 correctly apply temporarily and only to the process(es) in question themselves, whereas (3) can become "sticky" and even stick to processes created by the parent process while being restrained?
I suppose this is not news. But just want to confirm. And if true, (that only (3) is like that), the option to change affinity via ProBalance should come with a warning as such. :)
That's a good observation! I can confirm that if you were to use the CPU affinity option of ProBalance (few people do) it could propagate to child processes launched while the parent process is restrained. I've created a ticket to consider how to best address this and we will certainly at least add a warning about it.
Thanks for the heads up!