Commit 67cd88d
doc: fix typo in worker_threads.md
"Buffer.alloc()" -> "Buffer.allocUnsafe()"
Buffer.alloc() does not use the internal Buffer pool.
PR-URL: #38368
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>1 parent f1ea2c8 commit 67cd88d
1 file changed
Lines changed: 1 addition & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -666,7 +666,7 @@ Depending on how a `Buffer` instance was created, it may or may | |||
| 666 | 666 | not own its underlying `ArrayBuffer`. An `ArrayBuffer` must not | |
| 667 | 667 | be transferred unless it is known that the `Buffer` instance | |
| 668 | 668 | owns it. In particular, for `Buffer`s created from the internal | |
| 669 | - `Buffer` pool (using, for instance `Buffer.from()` or `Buffer.alloc()`), | ||
| 669 | + `Buffer` pool (using, for instance `Buffer.from()` or `Buffer.allocUnsafe()`), | ||
| 670 | 670 | transferring them is not possible and they are always cloned, | |
| 671 | 671 | which sends a copy of the entire `Buffer` pool. | |
| 672 | 672 | This behavior may come with unintended higher memory | |
0 commit comments