What I see is that in some cases. the chrome launcher reports it took 0ms to launch, and when that happens. the next attempt to make an API call results in ECONNREFUSED or ECONNREST. I assume this is a container lambda is reusing that had chrome already running. I don't mind doing some work and contribute to chromeless stability, but I need some guidance with the right apporach to this issue.