Fix --no-sandbox and --disable-gpu-sandbox on Mali.
On Mali GPUs we try to start the sandbox early, before the driver
spawns threads. Because of --no-sandbox, we don't actually start the
sandbox. |gpu_info.sandboxed| will then be false, so at the bottom of
the InitializeAndStartSandbox function we'll try to start the sandbox
again, but at this time the Mali driver will have already started
threads and we'll LOG(FATAL).
Fix by not attempting the second sandbox start when the early one
was attempted.
BUG=707461
TEST=Build for Kevin, add --no-sandbox to the cmdline, UI starts.
TEST=Add --disable-gpu-sandbox to the cmdline, UI starts.
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel;master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel
Review-Url: https://codereview.chromium.org/2814793007
Cr-Original-Commit-Position: refs/heads/master@{#466212}
Cr-Mirrored-From: https://chromium.googlesource.com/chromium/src
Cr-Mirrored-Commit: 754f1ec2c538c710a8a5bf304643acd89f106db0
1 file changed
