worker: do not send message if port is closing

Fixes: #42296

PR-URL: #42357
Reviewed-By: Anna Henningsen <[email protected]>
Reviewed-By: Antoine du Hamel <[email protected]>
Reviewed-By: Luigi Pinca <[email protected]>
Reviewed-By: Benjamin Gruenbaum <[email protected]>

Author: Trott

src/node_messaging.cc

@@ -964,7 +964,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;

test/parallel/test-worker-message-port-close.js

@@ -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');
+}