iheartcas.blogg.se

Copy and paste the entire output of the log command to a text file and attach it to the bug tracker. Then launch Chrome with with the -enable-sandbox-logging argument: open -a 'Google Chrome' -args -enable-sandbox-loggingĪfter you reproduce the issue, quit Chrome and Ctrl-C the log command to stop it. Start the log command to show sandbox violation errors: log stream -predicate '((processID = 0) AND (senderImagePath CONTAINS "/Sandbox")) OR (subsystem = "")' Sandbox violations are written to the system log (rather than Chrome's standard output/error), so a separate command is needed to access the data. If you have determined that the sandbox is responsible for the issue, the next step is to determine what the sandbox is blocking. If the issue no longer occurs, continue to help provide further debugging information. If the issue still persists, then the issue is not caused by the sandbox. After performing the test, you should quit Chrome and re-launch normally. Running with -no-sandbox is an insecure configuration. This can be done like so: open -a 'Google Chrome' -args -no-sandbox The easiest way to test if the sandbox is causing a compatibility issue is to temporarily disable it. Determining if the Sandbox is Responsible

This document provides instructions for debugging such issues.

It works by blocking the process from accessing OS resources, which can have unintended side effects that cause compatibility issues or crashes. The macOS sandbox confines Chrome processes that handle untrustworthy data or code (or both).