Skip to content

Commit

Permalink
doc: clarify synchronous blocking of Worker stdio
Browse files Browse the repository at this point in the history
Fixes: #25630
Signed-off-by: James M Snell <jasnell@gmail.com>
  • Loading branch information
jasnell committed May 13, 2021
1 parent 184e0f7 commit 01396c4
Showing 1 changed file with 24 additions and 0 deletions.
24 changes: 24 additions & 0 deletions doc/api/worker_threads.md
Expand Up @@ -1191,6 +1191,30 @@ active handle in the event system. If the worker is already `unref()`ed calling

## Notes

### Synchronous blocking of stdio

`Worker`s utilize message passing via {MessagePort} to implement interactions
with `stdio`. This means that `stdio` output originating from a `Worker` can
get blocked by synchronous code on the receiving end that is blocking the
Node.js event loop.

```js
'use strict';

const {
Worker,
isMainThread,
} = require('worker_threads');

if (isMainThread) {
new Worker(__filename);
for (let n = 0; n < 1e10; n++) {}
} else {
// This output will be blocked by the for loop in the main thread
console.log('foo');
}
```

### Launching worker threads from preload scripts

Take care when launching worker threads from preload scripts (scripts loaded
Expand Down

0 comments on commit 01396c4

Please sign in to comment.