mac-capture: Relocate static vars into coreaudio struct #12894
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
Relocating static variables into the instanced
coreaudiostruct that is passed into the thread to avoid a potential race condition? Granted, in this case, the variable seems to be initialized just fine so wasn't sure was this intended by the author? So not quite a 'bug'. Perhaps optional code cleanupMotivation and Context
The
input_callbackfunction is invoked by the Apple audio thread. We were setting up static variables here which is shared between both coreaudio input/output threads. I am not sure if that is intended or not? But cannot hurt to relocate this into the thread's coreaudio struct?How Has This Been Tested?
Verified in the debugger each thread has its' own
factorandinfovariables.Types of changes
Checklist: