rvagg/node-worker-farm

ERR_IPC_CHANNEL_CLOSED: Channel closed

Kikobeats opened this issue · 6 comments

Kikobeats commented

I'm experimenting this error using a more than one cpu for calculate fibonacci numbers.

events.js:136
      throw er; // Unhandled 'error' event
      ^

Error [ERR_IPC_CHANNEL_CLOSED]: Channel closed
    at process.target.send (internal/child_process.js:606:16)
    at callback (/Users/josefranciscoverdugambin/Projects/farm-cli/node_modules/worker-farm/lib/child/index.js:32:17)
    at /Users/josefranciscoverdugambin/Projects/farm-cli/node_modules/async/dist/async.js:958:16
    at check (/Users/josefranciscoverdugambin/Projects/farm-cli/node_modules/async/dist/async.js:3087:28)
    at Command.redis.get [as callback] (/Users/josefranciscoverdugambin/Projects/farm-cli/examples/fibonacci-redis/index.js:25:48)
    at normal_reply (/Users/josefranciscoverdugambin/Projects/farm-cli/node_modules/redis/index.js:726:21)
    at RedisClient.return_reply (/Users/josefranciscoverdugambin/Projects/farm-cli/node_modules/redis/index.js:824:9)
    at JavascriptRedisParser.returnReply (/Users/josefranciscoverdugambin/Projects/farm-cli/node_modules/redis/index.js:192:18)
    at JavascriptRedisParser.execute (/Users/josefranciscoverdugambin/Projects/farm-cli/node_modules/redis-parser/lib/parser.js:574:12)
    at Socket.<anonymous> (/Users/josefranciscoverdugambin/Projects/farm-cli/node_modules/redis/index.js:274:27)

reproducible code

This is what I'm running
https://github.com/Kikobeats/farm-cli/blob/master/examples/fibonacci-redis/index.js

git clone git@github.com:Kikobeats/farm-cli.git && cd farm-cli && npm install
redis-server &
DEBUG=farm-cli node ./bin/cli/index.js --cores 2 --workers 1 --delay 0 examples/fibonacci-redis --n 40

environment

node --version
v9.2.0
```

```
npm --version
5.5.1
```

Probably related with https://github.com/rvagg/node-worker-farm/pull/64
yoannmoinet commented

I'm experiencing this as well, but it happens very randomly.
It might not be related to the initial issue since it was opened 2 years ago.

> node -v
v.11.6.0

> yarn -v
1.13.0

Any info on this issue?

rvagg commented

closing this, perhaps it's improved with recent updates to Node? feel free to re-open but no promises I'll have any answers, maybe someone else will

psnehanshu commented

I am sill getting this issue

guybedford commented

I've been seeing this in 13.x recently too, for long-running workers (> 10mins) running at high CPU. Alternating with an EPIPE error as well.

  • 👍1
howel52 commented

any progress? get same error in node 15.9

Measy commented

Sill getting this issue too，in node 14.16.1