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.
IUnknown
to call.release()
automatically when objects go out of scopeUnloading COM support
section indoc/com.md
I'm worried that in some cases, if
.release()
is called (by Finalizer) after COM is unloaded due to call toCoUninitialize
, it'll lead to use after free that causes the process to crash, so I think it's better to let COM torn down when the process is terminated (we did something similar for WinRT and removed the mention ofwinrtUninitialize
which was callingRoUninitialize
Support automatic initialization of the WinRT and removewinrtUnitialize
helper function #642)