@Leo, this does appear to be caused/triggered by your settings on comment 16. At least on my MacBookPro15,1 model, after enabling those settings and reboot, I immediately encounter the same crash as you on Release and Nightly versions. It would be great to narrow down which setting is causing the crash to see if we can understand what's causing this. But given that this is an unsupported configuration (for Apple), it may be tough to get support. Could you try and determine which setting triggers this? I could not reproduce this with just SIP disabled. With your settings from comment 16, it is not reproducible with a local build which differs in not being notarized or signed which suggests it is triggered by one of the `com.apple.security` settings. -- Side note: for forcing crashes, we have `about:crashparent` and `about:crashcontent` pages for forcing crash reports in the parent and child process. Warning: they cause immediate crashes when loading the URL.
Bug 1722827 Comment 27 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
@Leo, this does appear to be caused/triggered by your settings on comment 16. On my `MacBookPro15,1 model`, after enabling those settings and rebooting, I immediately encounter the same crash as you on Release and Nightly versions. It would be great to narrow down which setting is causing the crash to see if we can understand what's causing this. But given that this is an unsupported configuration (for Apple), it may be tough to get support if this turns out to be an Apple issue. Could you try and determine which setting triggers this? I could not reproduce this with just SIP disabled. With your settings from comment 16, it is not reproducible with a local build which differs in not being notarized or signed which suggests it is triggered by one of the `com.apple.security` settings. -- Side note: for forcing crashes, we have `about:crashparent` and `about:crashcontent` pages for forcing crash reports in the parent and child process. Warning: they cause immediate crashes when loading the URL.
@Leo, this does appear to be caused/triggered by your settings on comment 16. On my `MacBookPro15,1` model, after enabling those settings and rebooting, I immediately encounter the same crash as you on Release and Nightly versions. It would be great to narrow down which setting is causing the crash to see if we can understand what's causing this. But given that this is an unsupported configuration (for Apple), it may be tough to get support if this turns out to be an Apple issue. Could you try and determine which setting triggers this? I could not reproduce this with just SIP disabled. With your settings from comment 16, it is not reproducible with a local build which differs in not being notarized or signed which suggests it is triggered by one of the `com.apple.security` settings. -- Side note: for forcing crashes, we have `about:crashparent` and `about:crashcontent` pages for forcing crash reports in the parent and child process. Warning: they cause immediate crashes when loading the URL.