-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exit always blocked after require() #474
Comments
We will investigate ASAP. Thanks for reporting! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Any time after
is called, the node script will not exit unless forced to. No other functions need to be called to see this behaviour. I've tried running wtfnode which will find open files, ports, timers, etc, etc and I get the following output:
MessagePort
implies (based on my really limited knowledge) that maybe a worker thread is opened somewhere? At a glance I'm not seeing what could be causing this, or any library you're using that might be using MessagePort or worker threads.The text was updated successfully, but these errors were encountered: