From 44131ad638c6c5ad59e220297fd3bb802fb5b1f9 Mon Sep 17 00:00:00 2001
From: Rich Trott <rtrott@gmail.com>
Date: Wed, 16 Mar 2022 06:16:00 +0000
Subject: worker: do not send message if port is closing

Fixes: https://github.com/nodejs/node/issues/42296

PR-URL: https://github.com/nodejs/node/pull/42357
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
---
 src/node_messaging.cc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'src/node_messaging.cc')

diff --git a/src/node_messaging.cc b/src/node_messaging.cc
index aac1245f269..6403950e9c8 100644
--- a/src/node_messaging.cc
+++ b/src/node_messaging.cc
@@ -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;
-- 
cgit v1.2.3