TracerContext construction might result in a terminate
Maintainers usually reply within 1 day
@akshat-lakhera is already working on this.
Since Oct 12, 2026.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 62/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- cpp
- Domain
- observability
Research direction
The problem is the TracerContext constructor in sdk/src/trace/tracer_context.cc, around line 38 at the linked commit, which is marked noexcept but can throw std::bad_alloc, so an allocation failure calls std::terminate. Start by reading that constructor and the members it allocates, then decide whether to drop the noexcept specifier or handle the allocation failure. Done means the constructor's exception behaviour matches its declaration and the project's existing tests still pass.
Written by the indexing model from the issue text.
Description
Constructor marked as noexcept and yet can throw on bad alloc
- Dominant language
- C++
- Stars
- 1.4k
- Forks
- 663
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 44
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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 open-telemetry/opentelemetry-cpp
-
Baggage::ToHeader/FromHeader use form-style `+` for space, which other W3C Baggage implementations read as a literal plusPossibly taken A pull request linked to this issue is open or already merged. Openbug triage/accepted
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
open-telemetry/opentelemetry-cpp#4745 · 1 comment ·
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
open-telemetry/opentelemetry-cpp#4697 · 1 comment ·
Maintainers usually reply within 1 day
-
[CI] Add Ubuntu 26.04 runners to the CI workflowMay be free again A pull request for this issue was closed without being merged. Opentriage/accepted
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
open-telemetry/opentelemetry-cpp#4596 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
[BUG] Resource::Create() throws bad_variant_access if process.executable.name isn't a stringMay be free again A pull request for this issue was closed without being merged. Openbug help wanted Stale triage/accepted
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
open-telemetry/opentelemetry-cpp#4535 · 2 comments · 2 reactions ·
Maintainers usually reply within 1 day
-
[BUG] OnResponse() can call std::terminate() when the response body fails to parse as JSON/protobufPossibly taken @YuEfSaEDU claimed this 62 days ago. Openbug help wanted Stale triage/accepted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
open-telemetry/opentelemetry-cpp#4534 · 3 comments · 1 reaction ·
Maintainers usually reply within 1 day
All issues in open-telemetry/opentelemetry-cpp
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
HarperFast/rocksdb-js#1118 ·
Maintainers usually reply within 1 day
-
bug triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
26.04 bug dark-mode Easy Hack impress symptom: visual
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
CollaboraOnline/online#16421 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
telegramdesktop/tdesktop#31653 ·
Maintainers usually reply within 1 day
-
area/cs bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
ydb-platform/ydb#59881 · 1 comment ·
Maintainers usually reply within 1 day