Skip to content

AtomicSafeInitializer.get() busy-spin without yield burns CPU during slow initialization#1651

Merged
garydgregory merged 1 commit into
apache:masterfrom
garydgregory:bugfix/AtomicSafeInitializer_better_init
May 17, 2026
Merged

AtomicSafeInitializer.get() busy-spin without yield burns CPU during slow initialization#1651
garydgregory merged 1 commit into
apache:masterfrom
garydgregory:bugfix/AtomicSafeInitializer_better_init

Conversation

@garydgregory
Copy link
Copy Markdown
Member

AtomicSafeInitializer.get() busy-spin without yield burns CPU during slow initialization.

  • Read the contribution guidelines for this project.
  • Read the ASF Generative Tooling Guidance if you use Artificial Intelligence (AI).
  • OP used AI to create the original report.
  • Run a successful build using the default Maven goal with mvn; that's mvn on the command line by itself.
  • Write unit tests that match behavioral changes, where the tests fail if the changes to the runtime are not applied. This may not always be possible, but it is a best practice.
  • Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
  • Each commit in the pull request should have a meaningful subject line and body. Note that a maintainer may squash commits during the merge process.

@garydgregory garydgregory force-pushed the bugfix/AtomicSafeInitializer_better_init branch from 7377818 to 12c213c Compare May 17, 2026 18:42
@garydgregory garydgregory merged commit b368d10 into apache:master May 17, 2026
50 of 52 checks passed
@garydgregory garydgregory deleted the bugfix/AtomicSafeInitializer_better_init branch May 17, 2026 20:01
garydgregory added a commit that referenced this pull request May 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant