Error RpcIpcMessagePortClosedError

I have a similar problem I want to share. Maybe its helpful to figure out what is the problem is. For this I will provide my setup here.

I came here from usage of nx running a node application. For development setup we run npm start (translates to) nx serve --runtimeArgs=--max-old-space-size=8192 --verbose which is doing a hot reload. I also added a DEBUG=* hoping to see something. Output is:

> nx run partner-api:serve --runtimeArgs=--max-old-space-size=2048 --verbose 
Hash: 816d7473c52e876f651b
Version: webpack 4.46.0
Built at: 10/12/2021 8:56:27 AM
              Asset      Size  Chunks                   Chunk Names
    assets/.gitkeep   0 bytes          [emitted]        
assets/swagger.json  1.61 KiB          [emitted]        
            main.js  25.2 KiB    main  [emitted]        main
        main.js.map  23.5 KiB    main  [emitted] [dev]  main
Entrypoint main = main.js main.js.map
Issues checking in progress...
  express:application set "x-powered-by" to true +0ms
  express:application set "etag" to 'weak' +2ms
  express:application set "etag fn" to [Function: generateETag] +0ms
  express:application set "env" to 'development' +1ms
  express:application set "query parser" to 'extended' +0ms
  express:application set "query parser fn" to [Function: parseExtendedQueryString] +0ms
  express:application set "subdomain offset" to 2 +0ms
  express:application set "trust proxy" to false +0ms
  express:application set "trust proxy fn" to [Function: trustNone] +1ms
  express:application booting in development mode +0ms
  express:application set "view" to [Function: View] +0ms
  express:application set "views" to '/app/views' +0ms
  express:application set "jsonp callback name" to 'callback' +0ms
  express:router use '/' query +1ms
  express:router:layer new '/' +0ms
  express:router use '/' expressInit +0ms
  express:router:layer new '/' +1ms
  express:router use '/' urlencodedParser +0ms
  express:router:layer new '/' +0ms
  express:router use '/' jsonParser +0ms
  express:router:layer new '/' +0ms
  express:router use '/docs' swaggerInitFn +1ms
  express:router:layer new '/docs' +0ms
  express:router use '/docs' serveStatic +0ms
  express:router:layer new '/docs' +0ms
  express:router use '/docs' <anonymous> +0ms
  express:router:layer new '/docs' +0ms
  express:router use '/swagger.json' serveStatic +0ms
  express:router:layer new '/swagger.json' +0ms
  express:router:route new '/partner/partner/:userId' +0ms
  express:router:layer new '/partner/partner/:userId' +1ms
  express:router:route get '/partner/partner/:userId' +0ms
  express:router:layer new '/' +0ms
Listening at http://localhost:3000/
No issues found.
Hash: 816d7473c52e876f651b
Version: webpack 4.46.0
Built at: 10/12/2021 8:56:47 AM
              Asset      Size  Chunks             Chunk Names
    assets/.gitkeep   0 bytes          [emitted]  
assets/swagger.json  1.61 KiB          [emitted]  
 + 2 hidden assets
Entrypoint main = main.js main.js.map

———————————————————————————————————————————————

here I changed a file and saved it.

>  NX   ERROR  Running target "partner-api:serve" failed

  Failed tasks:
  
  - partner-api:serve
  
  Hint: run the command with --verbose for more details.

node@774fa312c94c:/app$ node:internal/process/promises:246
          triggerUncaughtException(err, true /* fromPromise */);
          ^

RpcIpcMessagePortClosedError: Cannot send the message - the message port has been closed for the process 98.
    at /app/node_modules/fork-ts-checker-webpack-plugin/lib/rpc/rpc-ipc/RpcIpcMessagePort.js:47:47
    at processTicksAndRejections (node:internal/process/task_queues:82:21) {
  code: undefined,
  signal: undefined
}

The whole process is running in a docker container. Dockerfile.development:

FROM node:16-slim
RUN apt-get update && \
    apt-get install -y git && \
    rm -rf /var/lib/apt/lists/*

# build args (optional to change)
ARG UID=1000
ARG GID=1000
ARG USERNAME=node

# permissions
RUN mkdir /app
RUN mkdir /.npm
RUN chown node:node /app
WORKDIR /app
USER node

EXPOSE 3000
CMD npm start

docker_compose.yml

version: "3.9"
services:
  partnerapi:
    build:
      context: .
      dockerfile: Dockerfile.development
    user: "${DOCKER_UID:-node}:${DOCKER_GID:-node}"
    ports:
      - "3000:3000"
      - "9229:9229"
    networks: [a_network]
    volumes:
      - "../partnerapi:/app"

command to start:

DOCKER_UID=$(id -u) DOCKER_GID=$(id -g) docker-compose up partnerapi

My current “fix” is to add the restart: unless-stopped flag to the docker-compose, so at least it restarts after the crash.

My current assumption is, that there is a restriction in the IPC inside the docker (this is wild guess!). But maybe somebody with a deeper knowledge about this can see some connection I miss here.

Last note: The Issue disappears if the nx process is not running inside a docker container.

Thank you for the reply. I was testing it some more this afternoon and figured out I underestimated memory usage. Increasing RAM for the said virtual machine past 4 GB and increasing the swapfile helped and I am not getting this error any more. I apologize for opening the issue, since it is clear now, after solving the issue, that the problem was in my environement and not in the fork-ts-checker-webpack-plugin.