Currently Being ModeratedOct 17, 2012 11:54 AM (in response to onClick)
You're correct. See this thread. Don't be fooled by the fact that the question is marked as Solved.
I suggest that you Provide Feedback via the Numbers menu, contact AppleCare if you have it, see an Apple Store Genius if you are close to one.
If you have to work on a Numbers document, try to rest the "mouse" pointer off the table. The pointer has to be over the table, not the window as a whose, for the cpu to race.
Currently Being ModeratedOct 17, 2012 12:20 PM (in response to Jerrold Green1)
Wow, Jerrold! It's true. It's not that I didn't believe you at first, but I thought you were even joking, but no. I remove the mouse pointer from a table and the fan stops! I roll it over some and the fan starts again after some few seconds. How could that behavior escaped from my observations; I work with Numbers every day. Thanks a lot, man. Hope Apple issues a fix soon. Until then, I'll keep the rodent pointer away from any table as long as I can. I'll send a note to Apple right now; in my country there aren't Apple Store Geniuses.
Currently Being ModeratedOct 18, 2012 4:31 AM (in response to onClick)
You don't have to wait for the fans to start. You can look at the CPU load in Activity Monitor. It will jump to something on the order of 75% when the mouse hovers over a table. I was at first concerned that the problem was an interaction with third party apps. That happens, and even if it's only a small percentage of owners, they show up here and you think it's a universal problem. But in this case, you can walk into an Apple Retail Store and demonstrate the problem on the first computer you find.