{"version":"2.1.275","anchor":"ink-renderer-now-holds-frames-back-when-stdout-output-is-bac","canonical_anchor":"ink-renderer-now-holds-frames-back-when-stdout-output-is-bac","heading":"Ink renderer now holds frames back when stdout output is backlogged","tier":"notice","area":"Terminal Rendering","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275\/e\/ink-renderer-now-holds-frames-back-when-stdout-output-is-bac","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.275","markdown":"### Ink renderer now holds frames back when stdout output is backlogged\n\nTerminal UI now delays drawing new frames when output to the terminal is backed up\n\n**What**\n\nThe terminal interface's frame-pacing logic now checks how much output is still queued to be written to the terminal. If that backlog gets too large, it holds off scheduling the next frame and retries after a short delay, instead of always redrawing on a fixed time schedule regardless of how much output is waiting.\n\n**Why**\n\nThis should prevent the terminal display from piling up redraw work when output is already struggling to keep up, keeping the interface more responsive during heavy output.\n\n- Area: Terminal Rendering\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}