Change os_unfair_lock calls to use a dispatch queue instead. #837
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.
Goal
#832 shows a crash in
os_unfair_lock_unlock
that couldn't be traced back to anything user-side. Since we can't repro the issue, we need another way to defend against this.Design
os_unfair_lock
is a relatively new API, so it's not inconceivable that there could still be bugs in it. Dispatch queues, on the other hand, have been battle-hardened over decades. Dispatching to a local queue on a local thread has very low overhead, and will introduce far less latency than calling NSProcessInfo, so this will on the whole run faster.Changeset
bsg_mach_headers_add_image
now uses a dispatch queue rather thanos_unfair_lock
orOSSpinLock
.Testing
Re-ran all unit tests, and did manual tests to ensure end-to-end symbolication.