This entry was posted
on Wednesday, November 1st, 2006 at 11:35 pm and is filed under Mozilla.
You can follow any responses to this entry through the RSS 2.0 feed.
Both comments and pings are currently closed.
Didn’t want to set up an account on bugzilla, but I wanted to add a comment. I *think* 50% CPU on a dual-core OS X system means 100% of one core. So if the reporter is at a little over 50%, that means one thread is pegging one of his cores. Depending on what kind of ops it’s doing, that could easily kick the temperature into the stratosphere. Just wanted to get that said, to make sure people are looking for the right thing: a spinning, hard-working thread.
Someone (with a dual-core) should verify the 50% = 100% of one core thing.
Ben Morris, also from that crowd, reports that Firefox (all versions) on his Windows box also burns silicon, but at normal low CPU usage, even with no windows open. The chip just gets very very very hot while Firefox is running. Likely irreproducible.
November 2nd, 2006 at 9:11 am
That’s one heck of an interesting bug :)
November 5th, 2006 at 11:40 pm
I’m from this planet. We come in peace.
Didn’t want to set up an account on bugzilla, but I wanted to add a comment. I *think* 50% CPU on a dual-core OS X system means 100% of one core. So if the reporter is at a little over 50%, that means one thread is pegging one of his cores. Depending on what kind of ops it’s doing, that could easily kick the temperature into the stratosphere. Just wanted to get that said, to make sure people are looking for the right thing: a spinning, hard-working thread.
Someone (with a dual-core) should verify the 50% = 100% of one core thing.
Ben Morris, also from that crowd, reports that Firefox (all versions) on his Windows box also burns silicon, but at normal low CPU usage, even with no windows open. The chip just gets very very very hot while Firefox is running. Likely irreproducible.