nodejs
diff --git a/Collapse file
‎src/node_messaging.cc‎
Copy file name to clipboardExpand all lines: src/node_messaging.cc
+1-1Lines changed: 1 addition & 1 deletion b/Collapse file
‎src/node_messaging.cc‎
Copy file name to clipboardExpand all lines: src/node_messaging.cc
+1-1Lines changed: 1 addition & 1 deletion
diff --git a/Collapse file
‎test/parallel/test-worker-message-port-close.js‎
Copy file name to clipboardExpand all lines: test/parallel/test-worker-message-port-close.js
+8Lines changed: 8 additions & 0 deletions b/Collapse file
‎test/parallel/test-worker-message-port-close.js‎
Copy file name to clipboardExpand all lines: test/parallel/test-worker-message-port-close.js
+8Lines changed: 8 additions & 0 deletions
@@ -980,7 +980,7 @@ void MessagePort::PostMessage(const FunctionCallbackInfo<Value>& args) {
   // Even if the backing MessagePort object has already been deleted, we still
   // want to serialize the message to ensure spec-compliant behavior w.r.t.
   // transfers.
-  if (port == nullptr) {
+  if (port == nullptr || port->IsHandleClosing()) {
     Message msg;
     USE(msg.Serialize(env, context, args[0], transfer_list, obj));
     return;
 
@@ -39,3 +39,11 @@ function dummy() {}
     message: 'Cannot send data on closed MessagePort'
   });
 }
+
+// Refs: https://github.com/nodejs/node/issues/42296
+{
+  const ch = new MessageChannel();
+  ch.port1.onmessage = common.mustNotCall();
+  ch.port2.close();
+  ch.port2.postMessage('fhqwhgads');
+}