tonjik
In my case, as I mentioned earlier, it is mdworker that is using almost 100% of CPU usage. I should say WAS using almost 100% of CPU usage. Because I think I definitely fixed the problem.
I had installed Mountain Lion 10.8 over a Lion 10.7.4 clone on an external drive so as not to nuke my internal 10.7.4 in case something went wrong.
As all went well, and after a day or two of testing and updating, I "Carbon Copied" my working brand new Mountain Lion back to my internal drive. And that is when this mdworker 100% CPU usage started the overheating problem.
This morning, I remembered that yesterday, while cloning back my Mountain Lion installation to my internal drive, I had declined Carbon Copy's invitation to also create a 10.8 recovery partition, thinking that it wouldn't be of any use.
I then decided to start over Mountain Lion's cloning to my internal drive, but this time, WITH the installation of the 10.8 Recovery Partition.
I don't know how to explain – or if there is a link – but Mountain Lion is now working flawlessly on my internal drive, and mdworker seems happy and has been quiet for more than 2 hours now. My processor's temperatures went down from a steady 55-58 C yesterday to a mere 32-34 C eversince.
Anybody knows if there is a link between Spotlight indexation os a Mountain Lion partition and the existence or not of its relevant Recovery partition ?
YM