为提升您的使用体验,本站正在维护,部分功能暂时无法使用。如果本站文章无法解决您的问题,您想要向社区提问的话,请到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 提问,我们的支持社区将会很快回复您的疑问。

搜索 | 用户支持

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

详细了解

Firefox crashes on WebGL and Canvas pages (radeonsi_dri.so)

  • 2 个回答
  • 6 人有此问题
  • 9 次查看
  • 最后回复者为 crashprone

more options

Using Firefox 31 on Xubuntu, visiting pages which display WebGL or Canvas content produces very frequent crashes, with the cause apparently being a segfault when interacting with the radeon driver. One example that always produces a crash for me is the "Ninja Impact" example from the Phaser.js library. Other ones vary, but usually after viewing one or two WebGL applications (for example, the three.js demos), I get a crash.

Tried the nightly build - same result. No crashes on WebKit browsers.

See example crash here: https://crash-stats.mozilla.com/report/index/0deedd68-e6bc-4c52-b8f6-745962140730

Using Firefox 31 on Xubuntu, visiting pages which display WebGL or Canvas content produces very frequent crashes, with the cause apparently being a segfault when interacting with the radeon driver. One example that always produces a crash for me is the "Ninja Impact" example from the Phaser.js library. Other ones vary, but usually after viewing one or two WebGL applications (for example, the three.js demos), I get a crash. Tried the nightly build - same result. No crashes on WebKit browsers. See example crash here: https://crash-stats.mozilla.com/report/index/0deedd68-e6bc-4c52-b8f6-745962140730

所有回复 (2)

more options

That looks like a problem with the display driver (radeonsi_dri.so).

Is there an update available or can you try another (generic) display driver?

Are there any error messages on the troubleshooting information page in the Graphics section?

  • Help > Troubleshooting Information

You can try to disable hardware acceleration in Firefox.

  • Edit > Preferences > Advanced > General > Browsing: "Use hardware acceleration when available"

You need close and restart Firefox after toggling this setting.

more options

Disabling hardware acceleration didn't change anything. If this really were a driver problem, I would expect to see the same behavior in all browsers - WebKit based ones don't crash for me (and also have better WebGL performance).

Latest crash:

https://crash-stats.mozilla.com/report/index/31fca0e0-13ff-4501-8d5d-29c552140801