Repository navigation
OOM diagnostics: silence-scan breadcrumbs, unified log subsystem, separation kill switch - #85
Merged
sanylax0 merged 1 commit intoJul 18, 2026
Conversation
…aration kill switch Closes the diagnostic gaps found in the jetsam RCA: SilenceScan could decode ~32 MB buffers x3 with no breadcrumb; the mem breadcrumbs and StemSeparator logged under a different subsystem than every other logger (a single Console filter would hide them); and there was no way to rule the separation pipeline in or out of a repro without editing code. Adds silence-scan begin/end breadcrumbs, unifies all loggers on com.continuity.app, and adds a -debug.disableStemSeparation launch argument guard in ensureStems.
sanylax0
approved these changes
Jul 18, 2026
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
3 participants
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.
What
PR 1 of the jetsam RCA plan — closes the diagnostic blind spots so one instrumented run pins the eater:
mem[silence scan begin/end].MemoryFootprintandStemSeparatorlogged undercom.sanylax.continuitywhile every other logger usescom.continuity.app— a single Console filter would silently hide them. All oncom.continuity.appnow.-debug.disableStemSeparation YESmakesensureStemsa no-op, so one run can rule the whole ONNX pipeline in or out of the repro without code edits.How to run the diagnosis (from the approved plan)
mem[— the last breadcrumb before death names the stage: session load vswindow 0vs stair-stepping windows (→ separation), orseparation done/no breadcrumbs with smoothly decaying headroom (→ UI render ramp).JetsamEvent-*.ipsfrom Settings → Privacy & Security → Analytics Data for the footprint at kill.-debug.disableStemSeparation YESin the scheme's launch arguments — surviving that run confirms the separation branch.🤖 Generated with Claude Code
https://claude.ai/code/session_013TJoWkqg8bzkGdzxWhWjWP
Generated by Claude Code