{"version":"2.1.281","anchor":"heap-diagnostics-report-memory-correctly-on-bun","canonical_anchor":"heap-diagnostics-report-memory-correctly-on-bun","heading":"Heap diagnostics report memory correctly on Bun","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/heap-diagnostics-report-memory-correctly-on-bun","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Heap diagnostics report memory correctly on Bun\n\nThe memory report attached to a heap snapshot now has its own breakdown when Claude Code runs on Bun\n\n**What**\n\nA heap snapshot is a dump of the memory used by a running JavaScript program. The memory report that accompanies one now has a separate layout for Bun, one of the JavaScript runtimes Claude Code can run on. On Bun the report:\n\n- Reports the JS heap as heapUsed\n\n- Lists strings and buffers as \"part of the JS heap, in snapshot\"\n\n- Adds a line for memory \"outside the heap\"\n\nThe breakdown shown on Node (array buffers, other external, unaccounted) is unchanged.\n\n**Why**\n\nMemory figures in these diagnostics now match how Bun lays out its memory, so a report taken on Bun is easier to read correctly."}