open_or_create stuck in retry loop indefinitely on macOS aarch64 if retries are enabled
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- operating-systems
Research direction
Start with open_or_create on native macOS aarch64 and compare retry settings of 1 versus 2 or more, using the reported universal-binary build. Trace why the retry loop does not finish on arm64 while the x86_64 binary succeeds; done means open_or_create completes with retries enabled without regressing the other reported platforms.
Written by the indexing model from the issue text.
Description
Hi, I don't have an isolated repro case at the moment but wanted to share my findings. I have a cross-platform application that worked well with boost 1.66 on Linux x86_64, Linux ppc64le, Linux s390x, macOS x86_64, macOS aarch64 (M1). I upgraded to boost 1.81 and all platforms worked well except macOS aarch64. On that platform open_or_create sticks in a loop and never finishes. The two macOS platforms are compiled as a single universal binary with -arch x86_64 -arch arm64 mode using Apple clang version 14.0.0 (clang-1400.0.29.202). On the same M1 host, running the x86_64 binary under Rosetta emulation works, but the native aarch64 binary hangs. Changing BOOST_INTERPROCESS_MANAGED_OPEN_OR_CREATE_INITIALIZE_MAX_TRIES to 1 to disable the new retry behavior resolves the issue. If max tries is set to 2 or more it hangs. I'm happy to run any tests you recommend but I am unlikely to have time to try to whittle down my application to a self contained repro case for at least a few weeks. Thanks, Ryan
- Dominant language
- C++
- Stars
- 185
- Forks
- 131
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from boostorg/interprocess
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
boostorg/interprocess#196 · 1 reaction ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
boostorg/interprocess#279 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
boostorg/interprocess#274 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 28/100
boostorg/interprocess#268 · 4 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
boostorg/interprocess#262 · 2 comments ·
All issues in boostorg/interprocess
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
games-on-whales/wolf#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 76/100