{{ message }}
Expose per-thread untracked_memory in system.stack_trace#103065
Merged
Conversation
Contributor
Member
Author
|
On an empty server |
Adds a new `untracked_memory` column to `system.stack_trace` that reports the per-thread atomic-less allocation counter (`ThreadStatus::untracked_memory`) which has not yet been propagated to the parent `MemoryTracker`. The value is read in the signal handler running in the target thread's context (signal-safe, plain `Int64` load), and the type is `Int64` since the counter can go negative between flushes. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
686cc31 to
24205a1
Compare
serxa
approved these changes
Apr 18, 2026
Contributor
LLVM Coverage Report
Changed lines: 85.71% (24/28) · Uncovered code |
Member
Author
Merged
via the queue into
ClickHouse:master
with commit Apr 18, 2026
794c01e
157 of 161 checks passed
robot-clickhouse-ci-2
added a commit
that referenced
this pull request
Apr 20, 2026
Cherry pick #103065 to 26.1: Expose per-thread untracked_memory in system.stack_trace
robot-clickhouse
added a commit
that referenced
this pull request
Apr 20, 2026
This was referenced Apr 20, 2026
robot-clickhouse-ci-2
added a commit
that referenced
this pull request
Apr 20, 2026
Cherry pick #103065 to 26.2: Expose per-thread untracked_memory in system.stack_trace
robot-clickhouse
added a commit
that referenced
this pull request
Apr 20, 2026
This was referenced Apr 20, 2026
robot-clickhouse-ci-2
added a commit
that referenced
this pull request
Apr 20, 2026
Cherry pick #103065 to 26.3: Expose per-thread untracked_memory in system.stack_trace
robot-clickhouse
added a commit
that referenced
this pull request
Apr 20, 2026
clickhouse-gh Bot
added a commit
that referenced
this pull request
Apr 20, 2026
Backport #103065 to 26.1: Expose per-thread untracked_memory in system.stack_trace
azat
added a commit
that referenced
this pull request
Apr 21, 2026
Backport #103065 to 26.2: Expose per-thread untracked_memory in system.stack_trace
azat
added a commit
that referenced
this pull request
Apr 21, 2026
Backport #103065 to 26.3: Expose per-thread untracked_memory in system.stack_trace
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.

Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes into CHANGELOG.md):
Expose per-thread untracked_memory in system.stack_trace
Adds a new
untracked_memorycolumn tosystem.stack_tracethat reports the per-thread atomic-less allocation counter (ThreadStatus::untracked_memory) which has not yet been propagated to the parentMemoryTracker. The value is read in the signal handler running in the target thread's context (signal-safe, plainInt64load), and the type isInt64since the counter can go negative between flushes.Version info
26.4.1.105226.3.10.26,26.2.17.16,26.1.12.8