If this is not the correct place to file a bug, feel free to close it.
Using FF nightly with, when setting these prefs...
gfx.webrender.enabled --> true
gfx.webrender.blob-images --> true
... I get continuous insta-crashes upon (re-)starting the browser. Had to revert them from the prefs.js
All crash reports look exactly the same, except for the "Crash Reason", which sometimes is EXCEPTION_ACCESS_VIOLATION_READ or else EXCEPTION_ACCESS_VIOLATION_WRITE
Graphics card : AMD Mobility Radeon HD 5000 Series (with latest released driver for it)
This crash is being tracked here: https://bugzilla.mozilla.org/show_bug.cgi?id=1412848. I can't reproduce it locally, and don't have a theory about why it's crashing.
Can you try this with a fresh profile?
Can you try this with a fresh profile?
I started with Extensions disabled, and while the browser window stayed empty for a couple of seconds upon starting, it didn't crash.
Can you narrow down which extension might be related to crash?
Weird. I can not reproduce the problem when I install both of those extensions
Yes, there are a lot of users in the Nightly thread on Mozillazine forums, who use all kind of extensions, some including the extensions I mentioned, and most of them seem to experience no crashes. One other member who also uses a HD 5000 series graphics card experiences extreme long loading times. (That probably ain't related to my crashing problem)
Do you have any special font settings that you can think of?
Just chiming in to post my new findings.
Switching only _gfx.webrender.enabled_ to _true_ does NOT crash the browser, but there is a 5-6sec long blank browser window upon start.
It is the _gfx.webrender.blob-images_ entry, when set to _true_ that is insta-crashing the browser.
@Darkspirit figured out that the crash was happening only in 32bit builds. I can reproduce it now so it should be easy to fix.
A fix to this problem has landed. It should make it into tomorrow's Nightly build.
Closing this since it's fixed and tracked in https://bugzilla.mozilla.org/show_bug.cgi?id=1412848.
Most helpful comment
@Darkspirit figured out that the crash was happening only in 32bit builds. I can reproduce it now so it should be easy to fix.