Does Mozilla know macOS Nightly crashes every update?

Discussion about official Mozilla Firefox builds
Post Reply
burleigh
Posts: 28
Joined: October 6th, 2004, 8:13 am
Location: Bloomington, IN

Does Mozilla know macOS Nightly crashes every update?

Post by burleigh »

For about a week, Nightly crashes in a new way at every update. This new crash provokes the OS's "Problem Report" dialog, with this data:

Code: Select all

Process:               firefox [39603]
Path:                  /Applications/FirefoxNightly.app/Contents/MacOS/firefox
Identifier:            firefox
Version:               55.0a1 (5517.4.19)
Code Type:             X86-64 (Native)
Parent Process:        firefox [38650]
Responsible:           firefox [39603]
User ID:               501

Date/Time:             2017-04-19 09:04:47.241 -0400
OS Version:            Mac OS X 10.12.4 (16E195)
Report Version:        12
Anonymous UUID:        4E6EC1F0-163C-197D-41CD-28E2118700CE

Sleep/Wake UUID:       8105EC14-3235-42A4-B13C-27983329D491

Time Awake Since Boot: 150000 seconds
Time Since Wake:       3200 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGBUS)
Exception Codes:       KERN_PROTECTION_FAILURE at 0x000000010994b610
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Bus error: 10
Termination Reason:    Namespace SIGNAL, Code 0xa
Terminating Process:   exc handler [0]

VM Regions Near 0x10994b610:
    __DATA                 000000010993a000-000000010993b000 [    4K] rw-/rwx SM=COW  /Applications/FirefoxNightly.app/Contents/MacOS/libmozglue.dylib
--> __LINKEDIT             000000010993b000-0000000109951000 [   88K] r--/rwx SM=COW  /Applications/FirefoxNightly.app/Contents/MacOS/libmozglue.dylib
    MALLOC guard page      0000000109951000-0000000109952000 [    4K] ---/rwx SM=NUL  
Nightly's own fault/crash detector doesn't seem to catch this crash and, in fact, no crashes appear under about:crash since March 30.

Quitting Nightly sometimes provokes this crash, too -- I think.
Post Reply