[6.0] Fix named mutexes on OSX to work between arm64 and emulated x64 processes #62765
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.
Customer Impact
Some apps involving multiple processes may have x64 and arm64 .NET process components during transition, where the processes may try to share a named mutex for synchronization. Currently this is not possible, as the second process that tries to open an existing named mutex fails with an exception.
Regression?
No
Testing
Verified with a test case that a named mutex can be shared for synchronization between arm64 and emulated x64 .NET processes. Also verified backward compatibility between processes of the same arch.
Risk
Low, with a small caveat