unlockaccount spawns many nodejs defunct processes #1212
Labels
1.x
1.0 related issues
Enhancement
Includes improvements or optimizations
Stale
Has not received enough activity
I am getting a lot of [nodejs] [defunct] process when run this code. Is there a way to check if an account is already unlocked or lock the account to properly close the nodejs process it starts so that there are not too many nodejs defunct processes.
The text was updated successfully, but these errors were encountered: