feat: expose missing process APIs in sandboxed renderers (#13505)
This commit is contained in:
parent
f82f89b2a3
commit
fc85d02786
11 changed files with 95 additions and 35 deletions
|
@ -16,10 +16,19 @@ In sandboxed renderers the `process` object contains only a subset of the APIs:
|
|||
- `getHeapStatistics()`
|
||||
- `getProcessMemoryInfo()`
|
||||
- `getSystemMemoryInfo()`
|
||||
- `getCPUUsage()`
|
||||
- `getIOCounters()`
|
||||
- `argv`
|
||||
- `execPath`
|
||||
- `env`
|
||||
- `pid`
|
||||
- `arch`
|
||||
- `platform`
|
||||
- `resourcesPath`
|
||||
- `sandboxed`
|
||||
- `type`
|
||||
- `version`
|
||||
- `versions`
|
||||
|
||||
## Events
|
||||
|
||||
|
@ -68,6 +77,11 @@ instead of the `--no-deprecation` command line flag.
|
|||
|
||||
A `String` representing the path to the resources directory.
|
||||
|
||||
### `process.sandboxed`
|
||||
|
||||
A `Boolean`. When the renderer process is sandboxed, this property is `true`,
|
||||
otherwise it is `undefined`.
|
||||
|
||||
### `process.throwDeprecation`
|
||||
|
||||
A `Boolean` that controls whether or not deprecation warnings will be thrown as
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue