Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Node js module during the operation requests some resources on remote service, that better be released when it exits. We know that there is very nice:
process.on('exit', function() {
// ...
});
But then it is said that it won’t wait for any async operations to complete. So the question is if there’s any workaround (there should be some, since it’s quite widespread usage case)? Maybe one could start separate process or something?..
Only workaround I’ve seen is adding a wait loop and not finishing/returning from the .on(‘exit’, function until a property has been updated globally.
Totally a bodge-job design-wise, very bad practice, but I’ve seen it work for short calls (I think there is some timeout but I never bothered to look into the details).