Close environment if step raises an exception. #3043
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In #2988, that was raising with this callstack:
The actual error isn't that important, but the thing to note is that the worker process stuck was waiting for the main process :
ml-agents/ml-agents-envs/mlagents/envs/subprocess_env_manager.py
Line 104 in 2a0bb71
(I think, may have been somewhere different).
This means that the process never exited and basically deadlocked.
This change tries to call EnvManager.close() even if training raised an exception. I confirmed by undoing the fix from #2988 that this at least lets python exit and Unity stops playing (instead of having a spinning beach ball).