We currently support running Oxide in single process mode by setting the OXIDE_SINGLE_PROCESS environment variable, and I'd like an API to switch this on too. However, user scripts are currently a bit broken with single process mode. On the renderer side, we store BrowserContext-specific user script state process-wide, based on the assumption that a renderer process will not host views from more than one browsing context (which is true for non single-process mode).
We currently support running Oxide in single process mode by setting the OXIDE_SINGLE_ PROCESS environment variable, and I'd like an API to switch this on too. However, user scripts are currently a bit broken with single process mode. On the renderer side, we store BrowserContext- specific user script state process-wide, based on the assumption that a renderer process will not host views from more than one browsing context (which is true for non single-process mode).