{"version":"2.1.311","anchor":"new-mimalloc-env-vars-preserved-and-a-new-diagnostic-categor","canonical_anchor":"new-mimalloc-env-vars-preserved-and-a-new-diagnostic-categor","heading":"Two more memory-allocator environment variables are recognised","tier":"use","area":"Performance","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/new-mimalloc-env-vars-preserved-and-a-new-diagnostic-categor","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Two more memory-allocator environment variables are recognised\n\nClaude Code now lists `MIMALLOC_PURGE_DELAY` and `MIMALLOC_PURGE_HOLES` alongside `MIMALLOC_PURGE_HOLES_MIN_INTERVAL`, and adds new diagnostic categories\n\n**Unclear.** It is not clear what Claude Code does with the variables on this list, for example whether it passes them through or treats them specially.\n\n**What**\n\nMimalloc is a memory allocator, the part of a program that hands out and frees memory. Claude Code keeps a list of mimalloc environment variables (settings you can put in your shell before starting a program). That list used to hold only `MIMALLOC_PURGE_HOLES_MIN_INTERVAL`. It now also holds:\n\n- `MIMALLOC_PURGE_DELAY`\n\n- `MIMALLOC_PURGE_HOLES`\n\nA few new diagnostic categories were also added, used for Claude Code's internal reporting.\n\n**Why**\n\nThese are memory-tuning and reporting details that most people will not notice.\n\n- Area: Performance\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}