fix: explicitly start MessagePort (#116)

Co-authored-by: Ari Perkkiö <[email protected]>

Author: nazarhussain

src/entry/worker.ts

@@ -49,6 +49,8 @@ parentPort!.on('message', (message: StartupMessage) => {
     const readyMessage: ReadyMessage = { ready: true }
     parentPort!.postMessage(readyMessage)
 
+    port.start()
+
     port.on('message', onMessage.bind(null, port, sharedBuffer))
     atomicsWaitLoop(port, sharedBuffer)
   })().catch(throwInNextTick)

src/index.ts

@@ -791,6 +791,8 @@ class ThreadPool {
 
     worker.on('message', (message: ReadyMessage) => {
       if (message.ready === true) {
+        port1.start()
+
         if (workerInfo.currentUsage() === 0) {
           workerInfo.unref()
         }

src/runtime/process-worker.ts

@@ -92,6 +92,7 @@ export default class ProcessWorker implements TinypoolWorker {
     transferListItem?.forEach((item) => {
       if (item instanceof MessagePort) {
         this.port = item
+        this.port.start()
       }
     })
 
@@ -149,7 +150,7 @@ export default class ProcessWorker implements TinypoolWorker {
 
     // The forked child_process adds event listener on `process.on('message)`.
     // This requires manual unreffing of its channel.
-    this.process.channel?.unref()
+    this.process.channel?.unref?.()
 
     if (hasUnref(this.process.stdout)) {
       this.process.stdout.unref()