Re: Firefox trouble
On 7/14/20 8:02 PM, Connor McLaughlan wrote:
> Thread 1 "firefox" received signal SIGSEGV, Segmentation fault.
> MOZ_CrashOOL (aLine=<optimized out>, aReason=0xfffff8010b632bf0
> "js::jit::InitProcessExecutableMemory() failed")
> at /build/firefox-YyDH69/firefox-62.0.3/mfbt/Assertions.cpp:33
> 33 /build/firefox-YyDH69/firefox-62.0.3/mfbt/Assertions.cpp: No
> such file or directory.
See, that's the actual crash you were looking for.
> (gdb) bt
> #0 MOZ_CrashOOL (aLine=<optimized out>,
> aReason=0xfffff8010b632bf0 "js::jit::InitProcessExecutableMemory() failed")
> at /build/firefox-YyDH69/firefox-62.0.3/mfbt/Assertions.cpp:33
> #1 0xfffff801078134e0 in NS_InitXPCOM2 (aResult=0x700001ea770,
> aBinDirectory=<optimized out>,
> aAppFileLocationProvider=<optimized out>)
> at /build/firefox-YyDH69/firefox-62.0.3/xpcom/build/XPCOMInit.cpp:691
> #2 0xfffff8010a365638 in ScopedXPCOMStartup::Initialize (this=0x700001ea770)
> at /build/firefox-YyDH69/firefox-62.0.3/toolkit/xre/nsXREDirProvider.h:67
> #3 0xfffff8010a36dce8 in XREMain::XRE_main (this=0x7feffffdcb8,
> argc=<optimized out>, argv=<optimized out>,
> aConfig=...) at
> /build/firefox-YyDH69/firefox-62.0.3/toolkit/xre/nsAppRunner.cpp:4888
> #4 0xfffff8010a36e1d0 in XRE_main (argc=<optimized out>,
> argv=0x7fefffff378, aConfig=...)
> at /build/firefox-YyDH69/firefox-62.0.3/toolkit/xre/nsAppRunner.cpp:4984
> #5 0x0000010000006210 in do_main (argc=<optimized out>,
> argv=0x7fefffff378, envp=0x7fefffff388)
> at /build/firefox-YyDH69/firefox-62.0.3/build-browser/dist/include/mozilla/UniquePtr.h:326
> #6 0x0000010000005a98 in main (argc=<optimized out>,
> argv=0x7fefffff378, envp=0x7fefffff388)
> at /build/firefox-YyDH69/firefox-62.0.3/browser/app/nsBrowserApp.cpp:311
> (gdb)
So, this is an intentional crash here:
> /build/firefox-YyDH69/firefox-62.0.3/mfbt/Assertions.cpp:33
which is triggered by the function "js::jit::InitProcessExecutableMemory()" failing.
The Javascript memory management in Firefox can be nasty when running on an architecture
with virtual address spaces larger than 47 bits [1]. I suggest using an earlier Firefox
version (like 60).
It might also be an unrelated bug for which NetBSD is carrying a fix.
Adrian
> [1] https://bugzilla.mozilla.org/show_bug.cgi?id=1441473
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Reply to: