📣 Help shape Firefox by joining our Test Days event on July 21–Aug 1 to test the Firefox Semantic History Search in Firefox Beta 142

Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Dalše informacije

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

  • 2 wotmołwje
  • 6 ma tutón problem
  • 1 napohlad
  • Poslednja wotmołwa wot 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

Wšě wotmołwy (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