Branch 3538 (based on Chromium 70) changed the way helper processes are sandboxed, basically by eliminating the unsandboxed warmup phase (spanning from when the dynamic linker has loaded CEFswift/CEF up to the point CEFExecuteProcess was invoked). This will affect considerably how CEFswift may be used in the helper process, and I haven't yet figured out the answer.
To keep up with the builds, I decided to release 3538 half-baked. What this means to you as a CEF.swift end-user:
if you like to live dangerously, pass --disable-features=MacV2Sandbox to the browser process in the command line (note: it won't work forever) and keep using the helpers as before (see main.swift in CEFDemo for an example)
otherwise, for now you can either:
use (and optionally extend) the updated C/C++ helpers (I know, I know)
stay on branch 3497 that still uses the old sandboxing model
In the meantime, I'll try to come up with a definitive solution.
Branch 3538 (based on Chromium 70) changed the way helper processes are sandboxed, basically by eliminating the unsandboxed warmup phase (spanning from when the dynamic linker has loaded CEFswift/CEF up to the point
CEFExecuteProcesswas invoked). This will affect considerably how CEFswift may be used in the helper process, and I haven't yet figured out the answer.To keep up with the builds, I decided to release 3538 half-baked. What this means to you as a CEF.swift end-user:
--disable-features=MacV2Sandboxto the browser process in the command line (note: it won't work forever) and keep using the helpers as before (seemain.swiftin CEFDemo for an example)In the meantime, I'll try to come up with a definitive solution.
More info: