搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Firefox for Mac uses excessive CPU and makes laptop run hot

  • 1 个回答
  • 67 人有此问题
  • 9 次查看
  • 最后回复者为 Waseem Yaqoob

more options

Since installing Firefox 5, or the 6 Beta, my MacBook Pro i7 15 with 8Gb RAM runs extremely hot when using Firefox. I have made comparative measurements, each after a settling period of 30 minutes:

Firefox - CPU temperature 95 degrees, fan speed 6,000 rpm, using 182% of CPU, 28 threads, and 808Mb of memory.

Chrome 12 - CPU temperature 60 degrees, fan speed 2,500 rpm, using 0.09% of CPU, 19 threads, and 70Mb of memory.

Opera 11.5 - CPU temperature 55 degrees, fan speed 2,000 rpm, using 0.04% of CPU, 6 threads, and 85Mb of memory.

It does appear that there is a major fault in Firefox to use this amount of resource - and indeed it causes the laptop to run slowly and erratically too.

Any answers to fix this? I have tried disabling plugins, no difference.

Since installing Firefox 5, or the 6 Beta, my MacBook Pro i7 15 with 8Gb RAM runs extremely hot when using Firefox. I have made comparative measurements, each after a settling period of 30 minutes: Firefox - CPU temperature 95 degrees, fan speed 6,000 rpm, using 182% of CPU, 28 threads, and 808Mb of memory. Chrome 12 - CPU temperature 60 degrees, fan speed 2,500 rpm, using 0.09% of CPU, 19 threads, and 70Mb of memory. Opera 11.5 - CPU temperature 55 degrees, fan speed 2,000 rpm, using 0.04% of CPU, 6 threads, and 85Mb of memory. It does appear that there is a major fault in Firefox to use this amount of resource - and indeed it causes the laptop to run slowly and erratically too. Any answers to fix this? I have tried disabling plugins, no difference.

所有回复 (1)

more options

I've had this problem with Firefox 5. I deleted my profile and started a new one and the problem still persists. Also happens when I restart FF in safe mode with all extensions disabled, so I don't think they're the problem.

I'm on Lion, and didn't have such bad memory and CPU usage from Firefox before. Maybe that's something to do with it?