This may seem like a hardware post but it is not. This has to do with adobe flash and how it wastes a lot of energy. I've have been paying close attention the last couple of days of my CPU temperature. Yes I understand that when I use flash my CPU works harder and will generate more heat and raise my CPU temperature. What you may not know is that when you stop using flash that your CPU may continue to draw those extra watts of power and continue to do so until you restart your browser. This is what I've seen. Normal browsing with no flash my CPU draws from 2.5 watts to 6 watts on average, when flash is going my CPU jumps to 40 watts or more. Not a problem I understand that it's going to use more power because flash is a power hog. Problem is when I close the tab or window that contained the flash I would assume that my CPU would drop back down to the 4 watts it seems to average. That is not always the case, in fact more often than not it would not drop down until I restarted my browser, this was true in Firefox and Safari. So I started to restart Firefox after I would watch flash video, mainly twit.tv, I can't get enough of leo. That seemed to work for that part of the problem. However I use gmail for email and also use the gmail chat within it. When you receive a chat and it makes that little ding or dong or blip sound, that is flash, and it too caused my CPU to draw the 40 watts, and would not stop pulling the 40 watts until I restarted Firefox, not acceptable. You can turn off this in gmail chat settings, which I did. I am also now using a firefox add-on called flashblock. Now after I watch flash video and then close the window it seems that the CPU goes back down to its normal power usage. I will continue to watch closely to make certain that this is always the case. So if your system seems to run hot for no reason flash may be the problem. I am sure this has been discussed before, we all know flash is pretty evil but I always assumed that once you closed the window containing flash that the evilness went away, not always the case. I suggest you monitor your system and see if this is happening to you as well. Hopefully this is all fixed soon by whoever is responsible, Apple? Adobe? Intel? Gremlins?