Recording thread deadlock fix #1695
Merged
Conversation
This file contains 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.
This is a fix for a possible deadlock whenever recording thread is stopped, described in #1694.
The gist of this solution is that when
stopRecordingis called, GameThread no longer waits for FRecordingThread to finish — recording thread is let to run its course to completion. To be able to then start recording again, finishing thread is "moved aside" to another static variablefinishing_instance_inFRecordingThreadclass to free up therunning_instance_variable.When
EndPlayoccurs, FRecordingThread is given a chance to finish its course (same logic as was previously instopRecording). If it does not finish in a reasonable time though, it's just killed.