Her lead handed her the heap dump. A 14-gigabyte snapshot of Minotaur’s memory at the moment of death. “We have forty-five minutes before the morning traffic hits,” he said. “Find the leak.”

Inside: 7.4 million instances. Each one holding a HashMap of user preferences, a Date for last access, and—strangely—a byte[] that contained the user’s profile picture. Every. Single. Session.

The online analyzer offered a button. She clicked it. The shortest path was three hops. No soft references. No weak references. Just a steel chain of hard references from a static singleton.

And somewhere in a data center, Minotaur purred, its memory trimmed, its sessions finite, its ghosts finally released. Want a technical addendum (how such an online analyzer might actually work) or a sequel about another memory bug?

She clicked the view. The analyzer sorted objects by retained memory. The top offender was a class she didn’t recognize: CachedUserSession .

Maya’s pager screamed at 3:14 AM. The kind of scream that meant money was bleeding out.

She dragged the 14GB file into the browser window. A spinner. Three seconds.

She copied the stack trace, pasted it into Slack, tagged the backend team, and typed: Cache is immortal. Roll back. I’ll patch the eviction in twenty.