Mitchell Hashimoto

Ghostty's creator details a memory leak that caused the terminal emulator to consume up to 37 GB of memory after extended use. The bug stemmed from a scrollback optimization that reused pages but incorrectly reset metadata to standard size while leaving large mmap allocations intact, preventing munmap from being called. The issue became prominent with Claude Code's CLI, which produces many multi-codepoint graphemes requiring non-standard pages. The fix prevents reusing non-standard pages during scrollback pruning, instead properly freeing them and allocating fresh standard-sized pages from the pool.

Finding and Fixing Ghostty's Largest Memory Leak

<p>Am I the only one who thinks this whole thing with managing non-standard and standard pages was a bit over engineered.</p>


<p>We got used to it, why are they fixing it? Golden feature, when you move ghostty between displays and it got shut down all of a sudden, leaving the mouse pointer by itself, freeing all your claude code tabs. That should stay like more than a year so everyone will learn how to save the ids of sessions.</p>
