Skip to content

Commit 00b73a7

Browse files
chore: update ref to docs (🤖)
1 parent 949a158 commit 00b73a7

File tree

2 files changed

+8
-0
lines changed

2 files changed

+8
-0
lines changed

‎docs/latest/api/utility-process.md

+4
Original file line numberDiff line numberDiff line change
@@ -99,6 +99,8 @@ the child process exits, then the value is `undefined` after the `exit` event is
9999
```js
100100
const child = utilityProcess.fork(path.join(__dirname, 'test.js'))
101101

102+
console.log(child.pid) // undefined
103+
102104
child.on('spawn', () => {
103105
console.log(child.pid) // Integer
104106
})
@@ -108,6 +110,8 @@ child.on('exit', () => {
108110
})
109111
```
110112

113+
**Note:** You can use the `pid` to determine if the process is currently running.
114+
111115
#### `child.stdout`
112116

113117
A `NodeJS.ReadableStream | null` that represents the child process's stdout.

‎docs/latest/tutorial/fuses.md

+4
Original file line numberDiff line numberDiff line change
@@ -75,6 +75,10 @@ The onlyLoadAppFromAsar fuse changes the search system that Electron uses to loc
7575

7676
The loadBrowserProcessSpecificV8Snapshot fuse changes which V8 snapshot file is used for the browser process. By default Electron's processes will all use the same V8 snapshot file. When this fuse is enabled the browser process uses the file called `browser_v8_context_snapshot.bin` for its V8 snapshot. The other processes will use the V8 snapshot file that they normally do.
7777

78+
V8 snapshots can be useful to improve app startup performance. V8 lets you take snapshots of initialized heaps and then load them back in to avoid the cost of initializing the heap.
79+
80+
Using separate snapshots for renderer processes and the main process can improve security, especially to make sure that the renderer doesn't use a snapshot with `nodeIntegration` enabled. See [#35170](https://github.com/electron/electron/issues/35170) for details.
81+
7882
### `grantFileProtocolExtraPrivileges`
7983

8084
**Default:** Enabled

0 commit comments

Comments
 (0)