Current setup is that NativeProcess.destroy is creating a local variable hasBeenClosed and checking if the StdioHandle has been closed yet. This is not ideal.
When destroy is called, the lock should be obtained and, within the lock, a local variable created hasBeenDestroyed before setting isDestroyed to true. Then if hasBeenDestroyed is false, Workers should be destroyed. This is so that the Workers are destroyed once and only once.
Current setup is that
NativeProcess.destroyis creating a local variablehasBeenClosedand checking if theStdioHandlehas been closed yet. This is not ideal.When
destroyis called, the lock should be obtained and, within the lock, a local variable createdhasBeenDestroyedbefore settingisDestroyedto true. Then ifhasBeenDestroyedis false,Workers should be destroyed. This is so that theWorkers are destroyed once and only once.