54.0b1 & 54.0b2 exhibit the same problem, firefox starts, checks for addons updates, paints the first window with only the WM decoration and totally black area, then segfaults $firefox ATTENTION: default value of option force_s3tc_enable overridden by environment. ATTENTION: default value of option force_s3tc_enable overridden by environment. 1493186900308 addons.webextension.2.0@disconnect.me WARN Please specify whether you want browser_style or not in your browser_action options. 1493186901031 addons.webextension.jid1-MnnxcxisBPnSXQ-eff@jetpack WARN Loading extension 'jid1-MnnxcxisBPnSXQ-eff@jetpack': Reading manifest: Error processing options_page: An unexpected property was found in the WebExtension manifest. 1493186901466 addons.webextension.jid1-MnnxcxisBPnSXQ-eff@jetpack WARN Please specify whether you want browser_style or not in your browser_action options. Segmentation fault (core dumped) The top of the stack is always #0 0x0000000000000000 in ?? () #1 0x00001f2a2ea4c800 in _ZNSt6vectorIS_IhSaIhEESaIS1_EE19_M_emplace_back_auxIJS1_EEEvDpOT_ () from /usr/local/lib/firefox-54.0/libxul.so.71.0 which demangles to void std::vector<void*, std::allocator<void*> >::_M_emplace_back_aux<void* const&>(void* const&) - supposed to be in libstdc++, but the symbol is in libxul !? Crashes with and without e10s. I'd like help on what changed in 54/beta in terms of dependencies/default options/new codepaths that could trigger this - otherwise, that crash is beyond me. Putting this in core:graphics for lack of better option.. Fwiw, we use libstdc++ 4.2.1, but build firefox with clang 4.0, and link with binutils 2.17, if that matters. Yeah i know, frankeinstein toolchain.

(In reply to Landry Breuil (:gaston) from comment #0) > Fwiw, we use libstdc++ 4.2.1 Why not libc++ or newer libstdc++ as required by C++11 features like std::unique_ptr? Are all dependencies built against the same C++ library? Can you show complete stacktrace for a crash with e10s disabled? > #0 0x0000000000000000 in ?? () Build everything (not just firefox) with debugging symbols. Otherwise, don't strip non-debug symbols.

(In reply to Landry Breuil (:gaston) from comment #0) > paints the first window with only the WM decoration and totally black area, then segfaults Maybe related to bug 1345899.

Dammit, probably..i thought i had fixed it locally but it appears not. Will recheck then close this one as a dupe..

And of course 54.0b2 starts fine once i've put layers.enable-tiles to true in prefs.js. Now to find a better long-term solution there..