Why is the assumption that it's a bug?
If your index is large, it spins up all cores, because it's parallelized in recent versions.
You know, doing what it's supposed to do.
If your index is large, it spins up all cores, because it's parallelized in recent versions.
You know, doing what it's supposed to do.
The option to use spotlight as a calculator is part of its feature set. And the fact that it still does recognize (after a lot of cpu usage) that I wanted to make a calculation does indicate that the calculator functionality is still there. It just seems to be triggering some huge operation that requires even more cpu usage than a normal spotlight search.