In other words: Probably not Firefox's fault. The Firefox devs probably started adding support for accelerating more stuff via the GPU via OpenGL calls and if your driver has issues with any of those calls (e.g. bad application auto-detection) it can cause things to crash or have undefined behavior.
Not much the Firefox devs can do about it but report the bug anyway. At the very least they might be able to figure a workaround.
If I understand it correctly, that's one of the perks of WebRender: by using the GPU more like a game engine would, we're relying on code paths that tend to be better tested / more reliable.
A few switches of relevance: layers.acceleration, webgl.disabled, media.hardware-video-decoding.enabled, gfx.webrender.force-disabled