|
First I'd like to thank the developer for this excellent tool which I use everyday!
Now on to the real business of this post: using 1.4.9b4 (the bug was not listed on the b5 changelog, so I assume it still exists in b5), I notice that even though it is set to remember to use Low priority, if it is started up and fresh files loaded and indexing is started, priority remains Normal, as observed in the Task Manager. Sometimes this happens and sometimes not.
However, if indexing is stopped and priority is switched to Normal then back to Low, it actually runs at Low. Also, it seems to regularly forget the priority setting when starting up (ie. Normal will be checked even though Low was set last sesssion). So there's definitely some bugs in the priority code.
|