On Tue, Sep 18, 2018 at 02:30:03PM +0900, Mike Hommey wrote: > On Tue, Sep 18, 2018 at 05:26:43PM +1200, Tim Makarios wrote: > > On 18/09/18 17:05, Mike Hommey wrote: > > > Oh, right. Forgot about the crash reporter interposing itself. You can > > > do one of the following: > > > ... > > > - or send the report to Mozilla, and find its id in > > > ~/.mozilla/firefox/Crash Reports/submitted > > > ... > > > > I'd already reported a few earlier crashes to Mozilla, but I did it again > > today, and the most recent file in that directory contains just the line: > > > > Crash ID: bp-a47d7854-9ea2-4c6b-b432-4b98e0180918 > > > > Is that what you're looking for? > > Yes, thanks.
So the crash is happening in JITed code, which is not expected: the JIT should disable itself. There might be something wrong either in the detection or maybe some parts don't disable themselves as they're supposed to. Can you try starting with `firefox-esr -safe-mode`? If that works, can you then go to about:config and switch javascript.options.ion to false, then restart without -safe-mode? If that works, stop there. If it doesn't work, can you try -safe-mode again, and switch javascript.options.baselinejit to false? Can you then report what worked and what didn't? Thanks Mike
