You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our app uses the prom-client for updating several counters, via worker threads as well as the main thread. Whenever we do a deployment of our app, and if a worker thread with one of the counters active is interrupted it will give the following error
The Likely Cause
It's these lines that are likely causing this error (as can be seen in the stack trace). The worker issuing the process.send has disconnected, and so when the process.send call is made it triggers this error.
It's the same as an issue seen nearly 3 years ago - #244.
A likely fix for this would be to wrap those process.send calls using:
if ( process.connected ) {
// do the process.send here
}
Hope that provides enough information for this issue.
The text was updated successfully, but these errors were encountered:
ingeniumed
changed the title
[BUG] ERR_IPC_CHANNEL_CLOSED showing up on deployment
[BUG] ERR_IPC_CHANNEL_CLOSED showing up on new deployments
Apr 5, 2023
The Problem
Our app uses the prom-client for updating several counters, via worker threads as well as the main thread. Whenever we do a deployment of our app, and if a worker thread with one of the counters active is interrupted it will give the following error
The Likely Cause
It's these lines that are likely causing this error (as can be seen in the stack trace). The worker issuing the process.send has disconnected, and so when the process.send call is made it triggers this error.
It's the same as an issue seen nearly 3 years ago - #244.
A likely fix for this would be to wrap those process.send calls using:
Hope that provides enough information for this issue.
The text was updated successfully, but these errors were encountered: