Fix hwdevice being destroyed before context causing sigsegv on AMD#88
Merged
ReenigneArcher merged 2 commits intoLizardByte:nightlyfrom Mar 13, 2022
Merged
Conversation
…e the context relies on the hwdevice still being active.
…s destroyed in the correct order.
Contributor
Author
|
I've updated it slightly so the order of the members won't matter, instead the session_t destructor will ensure they're destroyed in the correct order. |
Member
|
I can't test this, but both code and rationale seems reasonable. LGTM |
TheElixZammuto
approved these changes
Mar 13, 2022
2 tasks
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 bad sigsegv on AMD GPUs (maybe others too, though I've only seen it reported on AMD) running on Linux. Basically, because of the order of the members in session_t, hwdevice would be destroyed before the avcodec context. This causes problems because the context relies on the hwdevice still being active - as in, when the hwdevice is destroyed the dri library is unloaded, and va calls methods in there.
Here's a backtrace of the sigsegv:
Screenshot
Include screenshots if the changes are UI-related.
Issues Fixed or Closed
Type of Change
Checklist