{"version":"2.1.317","anchor":"startup-memory-note-records-bun-gc-timer-disable","canonical_anchor":"startup-memory-note-records-bun-gc-timer-disable","heading":"Startup memory diagnostics now note whether BUN_GC_TIMER_DISABLE is set","tier":"internal","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/startup-memory-note-records-bun-gc-timer-disable","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Startup memory diagnostics now note whether `BUN_GC_TIMER_DISABLE` is set\n\nClaude Code's startup memory record now also notes whether `BUN_GC_TIMER_DISABLE` is set, next to `MIMALLOC_PURGE_DELAY`\n\n**What**\n\nAt startup Claude Code writes a diagnostic record of memory-related environment variables. Environment variables are settings you can put in your shell before starting a program. Alongside `MIMALLOC_PURGE_DELAY`, the record now also notes whether `BUN_GC_TIMER_DISABLE` is set. That variable relates to Bun, the runtime Claude Code is built on, and to the timer for its garbage collection, the automatic freeing of memory that is no longer used.\n\nThe recorded purge delay is also no longer cleared when an error occurs.\n\n**Why**\n\nThis is diagnostic data only. It lets memory behaviour be compared against garbage collection settings, and it does not change how Claude Code runs.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}