(In reply to Francois Guerraz from comment #12) > (In reply to Gian-Carlo Pascutto [:gcp] from comment #10) > > Arch seems to be using its own build which we have no symbols for so there's no way for us to make sense of that stack. > > This is my own build, any tips on the build config to make the backtrace more usable? > > With the official firefox nightly, I get this backtrace bp-1cd73931-a2b0-48fb-a372-279790201026 which points to bug 1672558. > > Thank you. you must have been setting media.rdd-ffmpeg.enable to true which you shouldn't ; and there's no reason today why you would want to set that pref unless you're a mozilla dev.
Bug 1660131 Comment 13 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Francois Guerraz from comment #12) > (In reply to Gian-Carlo Pascutto [:gcp] from comment #10) > > Arch seems to be using its own build which we have no symbols for so there's no way for us to make sense of that stack. > > This is my own build, any tips on the build config to make the backtrace more usable? > > With the official firefox nightly, I get this backtrace bp-1cd73931-a2b0-48fb-a372-279790201026 which points to bug 1672558. > > Thank you. you must have been setting media.rdd-ffmpeg.enable to true which you shouldn't ; and there's no reason today why you would want to set that pref unless you're a mozilla dev. And I believe you've been given that exact same information in another bug.