Long-running server processes (Java's old CMS garbage collector before G1, and glibc malloc's arena behavior) have historically been forced into scheduled restarts purely because external fragmentation made previously-freed memory unusable for new large allocations, a phenomenon that's invisible until you visualize the heap layout the way this task does. Tools like jemalloc's stats.print() and Java's GC logs exist specifically to expose this same free-space-versus-usable-space gap that ASCII-art rendering makes intuitive here.