Fix controller activation crash on macOS (Fixes #604) (backport #2391) #2396
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 PR resolves #604, which caused a runtime crash on macOS during controller activation.
The issue stemmed from the use of std::defer_lock with std::unique_lock prior to calling wait() on a condition variable. On macOS, the underlying libc++ implementation strictly enforces that a mutex must be locked before invoking wait(). Since defer_lock does not acquire the lock, this led to undefined behavior and a crash at runtime.
This PR corrects the locking behavior by ensuring the mutex is properly locked before wait() is called, making the code safe and portable across platforms, including macOS.
This is an automatic backport of pull request #2391 done by Mergify.