Remove invalid reads after delete in DeviceContextFinished #1239
+3
−2
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
In DeviceContextFinished(), interop->GetDefaultFree() and interop->GetDefaultUserOpaque() were called after interop was deleted. These invocations have been moved to before the destruction of interop. Resolves: MythTV#1166
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 DeviceContextFinished(), interop->GetDefaultFree() and interop->GetDefaultUserOpaque() were called after
interop was deleted. These invocations have been moved to before the destruction of interop. This update eliminates two "Invalid read of size 8" errors reported by valgrind.
Resolves: #1166
Checklist