Repository navigation
Log a ~10s memory heartbeat during playback - #90
Merged
sanylax0 merged 1 commit intoJul 18, 2026
Merged
Conversation
The latest jetsam took a full song of plain playback with zero ingest activity — a window no existing breadcrumb covers. tick() now logs os_proc_available_memory every ~10 s while playing, so the next kill's console shows the decay slope (how fast, from what baseline) instead of silence.
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
The latest kill survived a full song of plain playback with zero breadcrumbs in the console — the stem pipeline never ran, so the remaining eater lives in a window no existing instrumentation covers.
Player.tick()now logsos_proc_available_memoryevery ~10 s while playing (mem[playback] N MB headroom, categoryaudio).Why this matters
The next kill's console gives three numbers we currently lack: the headroom baseline right after play starts (reveals the actual iOS 26 per-process budget), the decay slope (MB lost per 10 s — a leak rate), and the floor at the last line before death. That discriminates the remaining suspects (per-tick animation churn in the leaves, artwork/URLCache growth, AVAudioEngine/timePitch internals, or a system-wide
vm-pageshortagekill that isn't the app's fault at all — the JetsamEventreasonfield cross-checks that last one).Ask
After merging: reproduce once and paste all the
mem[playback]lines plus the top ~15 lines of the newestJetsamEvent-*.ips(especiallyreasonand the app's footprint).🤖 Generated with Claude Code
https://claude.ai/code/session_013TJoWkqg8bzkGdzxWhWjWP
Generated by Claude Code