Skip to content

Commit e757122

Browse files
authored
doc: remove reference to resolved child_process v8 issue
The linked v8 issue is closed. The NodeJS half of that issue has also been resolved. While there still may be issues related to child_process spawn performance, they are not related to this v8 issue. Refs: https://bugs.chromium.org/p/v8/issues/detail?id=7381 Refs: nodejs#48523 Refs: nodejs/performance#138
1 parent 94f824a commit e757122

File tree

1 file changed

+1
-3
lines changed

1 file changed

+1
-3
lines changed

doc/api/child_process.md

+1-3
Original file line numberDiff line numberDiff line change
@@ -875,9 +875,7 @@ normally without the process being held open by the open IPC channel._
875875

876876
On Unix-like operating systems, the [`child_process.spawn()`][] method
877877
performs memory operations synchronously before decoupling the event loop
878-
from the child. Applications with a large memory footprint may find frequent
879-
[`child_process.spawn()`][] calls to be a bottleneck. For more information,
880-
see [V8 issue 7381](https://bugs.chromium.org/p/v8/issues/detail?id=7381).
878+
from the child.
881879

882880
See also: [`child_process.exec()`][] and [`child_process.fork()`][].
883881

0 commit comments

Comments
 (0)