Fix / Avoid double Release() in FindCaptureDevice() #65
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.
Description
This fixes a semantic conflict from merging 5e8b963 of #53 which inside
FindCaptureDevice()
was usingScopedComPtr<>
to handle ownership ofpMoniker
implicitly, and 58d4be4 of #52 which was using an explicitRelease()
onpMoniker
. Both by @sandman42292 in time- and branch-overlapping PRs.Justification
Crashes on Windows.
Testing
Tested with
win/test/openpnp-capture-test.exe
. This crashed before and now works.I was unable to test this in OpenPnP, due to lack of knowledge of how to put the dll "into" Java, in a development environment, i.e., make it override maven artifacts. 😅
Instructions welcome!