enum | OxideProcessModel { OxideProcessModelMultiProcess, OxideProcessModelSingleProcess } |
QString | oxideGetChromeVersion() |
size_t | oxideGetMaxRendererProcessCount() |
QString | oxideGetNSSDbPath() |
OxideProcessModel | oxideGetProcessModel() |
QString | oxideGetVersion() |
void | oxideSetMaxRendererProcessCount(size_t count) |
void | oxideSetNSSDbPath(const QString & path) |
void | oxideSetProcessModel(OxideProcessModel model) |
Constant | Value | Description |
---|---|---|
OxideProcessModelMultiProcess | 0 | Multi-process mode. In this mode, web content runs in sandboxed sub-processes rather than the application process. This mode provides the best level of security and fault tolerance. |
OxideProcessModelSingleProcess | 1 | Single process mode. In this mode, web content runs in the application process. Web content is not sandboxed, and crashes that would normally only affect a web content process in multi-process mode will result in an application crash in this mode. |
Return the Chromium version that this Oxide build is based on, in the form x.x.x.x.
This function was introduced in OxideQt 1.15.
Return the maximum number of web content processes that Oxide will run. If oxideSetMaxRendererProcessCount has not been called, this will return a system-dependent default.
See also oxideSetMaxRendererProcessCount.
Returns the custom directory that Oxide will look in for the NSS database. This will return an empty string if the application hasn't called oxideSetNSSDbPath, or this is a build of Oxide that doesn't use NSS.
See also oxideSetNSSDbPath.
Returns the current process model. The default (if the application hasn't called oxideSetProcessModel) will be OxideProcessModelMultiProcess.
See also oxideSetProcessModel.
Return the current Oxide version, in the form 1.x.x.
This function was introduced in OxideQt 1.15.
Set the maximum number of web content processes to run. Setting this to 0 will reset it to the default, which is system dependent.
This is not a hard limit, as there are cases where web content processes will not be shared (eg, web views in different web contexts, or incognito / non-incognito web views).
This must be called before Oxide is started up (in your applications main(), before using any other Oxide APIs). Calling it afterwards will have no effect.
See also oxideGetMaxRendererProcessCount.
Call this to specify a custom directory to look in for the NSS database. If this isn't called, then Oxide will use the NSS shared database.
This must be called before Oxide is started up (in your applications main(), before using any other Oxide APIs).
This has no effect if the build of Oxide does not use NSS.
This function is mostly only useful for testing purposes.
See also oxideGetNSSDbPath.
Set the desired process model. This determines whether Oxide will run web content in sandboxed sub-processes or the application process.
This must be called before Oxide is started up (in your applications main(), before using any other Oxide APIs). Calling it afterwards will have no effect.
See also oxideGetProcessModel.