User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:58.0) Gecko/20100101 Firefox/58.0 Build ID: 20171111220358 Steps to reproduce: Visited https://maierfelix.github.io/wasm-particles/static/ with Nightly Firefox v58.0a1 (2017-11-11) (64-bit) with `gfx.webrender.enabled` set to `true`. Actual results: Firefox crashes immediately. Expected results: The WebGL demo using WASM should have displayed (and does with webrender turned off).

Interestingly this site worked on the Nightly from Friday nov 10, so it seems like a recent regression.

Nightly 58 x64 20171112100435 de_DE aabfc14671b55983e1c3053989a4c3b7c5691aaa @ Debian Testing (KDE, Radeon RX480) fresh profile: layers.acceleration.force-enabled, gfx.webrender.enabled, (also tested: gfx.webrender.blob-images) WFM on Linux, but I only have 32-33 fps (chromium: 25 fps). (Someone else will check on Mac.) (I also checked yesterday's builds with mozregression and all were fine.)

(In reply to David Palm from comment #0) Can you find relevant crash reports on about:crashes? (One or multiple reports from the same time when you tested this.)

This was the first crash report: https://crash-stats.mozilla.com/report/index/1cbdbd7f-fb62-46ca-b752-67faf0171106#tab-extensions This is the last of several (using today's Nightly): https://crash-stats.mozilla.com/report/index/66c7b181-96f6-472f-8953-2d7f80171112 This is on a Mac.

I can also reproduce on a mac, https://crash-stats.mozilla.com/report/index/2e101ddd-b781-47fd-a708-aa4dd0171112

I also confirmed the crash with http://learningwebgl.com/lessons/lesson03/index.html. From it, the crash seems to happen generally with WebGL with WebRender. I take a look.

bug 1410186 seems to be related and it just seems to expose hidden bugs.

Confirmed that attachment 8927719 [details] [diff] [review] addressed the crash.

Pushed by sikeda@mozilla.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/b72a76a98bef Add SurfaceFormat::R8G8B8A8 handling to SurfaceFormatToImageFormat() r=nical

I have managed to reproduce the issue mentioned in comment 0 using Firefox 58.0a1 (BuildId:20171112220346). This issue is no longer reproducible using Firefox 60.0a1 (BuildId:20180129220114) and Firefox 59.0b5 (BuildId:20180128191456) on macOS 10.13.2.