worker: handle detached MessagePort from a different context

When `worker.moveMessagePortToContext` is used, the async handle
associated with the port, will be triggered more than needed (at least
one more time) and with null data. That can be avoided by simply
checking that the data is present and the port is not detached.

Fixes: nodejs#49075
Signed-off-by: Juan José Arboleda <soyjuanarbol@gmail.com>

src/node_messaging.cc

@@ -795,6 +795,11 @@ void MessagePort::OnMessage(MessageProcessingMode mode) {
 
   size_t processing_limit;
   if (mode == MessageProcessingMode::kNormalOperation) {
+    // Maybe the async handle was triggered empty or more than needed
+    // (called twiced on a new context).
+    if (GetTransferMode() == TransferMode::kDisallowCloneAndTransfer || !data_)
+      return;
+
     Mutex::ScopedLock(data_->mutex_);
     processing_limit = std::max(data_->incoming_messages_.size(),
                                 static_cast<size_t>(1000));