Workaround race condition in ShutdownAPI and logging and custom mem mngmt #2859
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.
Issue #, if available:
TEST(AwsMemoryManagementTest, MultiInitParallel)
fails once in a blue moon with sanitizer report in case of custom memory management enabled.It is not an issue in case of basic-use non-violated.
We really need to refactor the InitAPI-ShutdownAPI design...
Description of changes:
Preserve the logger for some time to let all pending logging statements to finish.
This is a workaround not a real fix.
Check all that applies:
Check which platforms you have built SDK on to verify the correctness of this PR.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.