搜索 | 用户支持

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

详细了解

Firefox for Linux media, videos, maps much slower and resource intensive than Chrome

  • 1 个回答
  • 1 人有此问题
  • 2 次查看
  • 最后回复者为 typhooncamel

more options

I am partial to running Firefox over Chrome, however, there are several instances when the difference between the two is abysmal.

Whenever I play any videos (for example Youtube), browse any maps (Nokia Here, Google Maps), or do anything that requires media (Skype, Google Hangouts), Firefox is slow, a single core will go to 100%, Firefox will become slow to respond, and sometimes will hang. On the other hand, these same sites on Google Chrome (or Chromium) will be perfectly smooth and fast.

I have searched for several solutions, including enabling/disabling hardware acceleration, checking that addons are not the culprit, checking that the plugins are up to date, and so on, to no avail. I have also followed Mozilla's "high CPU" and "high RAM" pages, but finding no solution.

I am currently running Firefox 44 on Ubuntu 14.04. Does anyone have any suggestions?

I am partial to running Firefox over Chrome, however, there are several instances when the difference between the two is abysmal. Whenever I play any videos (for example Youtube), browse any maps (Nokia Here, Google Maps), or do anything that requires media (Skype, Google Hangouts), Firefox is slow, a single core will go to 100%, Firefox will become slow to respond, and sometimes will hang. On the other hand, these same sites on Google Chrome (or Chromium) will be perfectly smooth and fast. I have searched for several solutions, including enabling/disabling hardware acceleration, checking that addons are not the culprit, checking that the plugins are up to date, and so on, to no avail. I have also followed Mozilla's "high CPU" and "high RAM" pages, but finding no solution. I am currently running Firefox 44 on Ubuntu 14.04. Does anyone have any suggestions?

所有回复 (1)

more options

I have eventually found what probably was the culprit

gfx.xrender.enabled

which needs to be set to false in my case.