Remove destructor logging #424
Closed
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.
So this came up while working on another PR, but it turns out logging in destructors was causing issues after all. In particular the
RobotClient
destructor may run afterInstance
(and henceLogManager
) have already been destroyed. I encountered this when joining threads inRobotClient::close
was throwing an exception due to joining an unjoinable thread, so that will probably need a separate hotfix, but we should merge this one soon.