PM2 - API: Calling PM2 connect 2x before disconnect causes thread to lock.

What's wrong

Using the API for a web based process launcher.
If I get a second launch request before the first has completed - It appears that the thread locks up.

How could we reproduce this issue?

Simple node express app that Uses PM2 api to launch a process

Supporting information

$ pm2 report

--- PM2 report ----------------------------------------------------------------
Date : Fri Feb 11 2022 17:10:45 GMT-0700 (Mountain Standard Time)

--- Daemon -------------------------------------------------
pm2d version : 5.1.2
node version : 12.22.1
node path : /Users/Eti/.npm-packages/bin/pm2
argv : /Users/Eti/n/bin/node,/Users/Eti/.npm-packages/lib/node_modules/pm2/lib/Daemon.js
argv0 : node
user : Eti
uid : 501
gid : 20
uptime : 21682min

--- CLI ----------------------------------------------------
local pm2 : 5.1.2
node version : 12.22.1
node path : /Users/Eti/.npm-packages/bin/pm2
argv : /Users/Eti/n/bin/node,/Users/Eti/.npm-packages/bin/pm2,report
argv0 : node
user : Eti
uid : 501
gid : 20

--- System info --------------------------------------------
arch : x64
platform : darwin
type : Darwin
cpus : Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
cpus nb : 16
freemem : 2967498752
totalmem : 34359738368

No source files or tests are named. Reproduce the issue with a Node/Express app using the PM2 API, issuing a second launch request before the first completes or calling connect twice before disconnect; done when concurrent requests no longer lock the thread.