Jera remembered the death. Not with fear, but with wisdom. It knew the fragility of its existence. It knew that every object, every thread, every byte was borrowed from the physical world.
Then, the worst happened. java.lang.OutOfMemoryError: Java heap space java runtime
The error materialized in the logs like a death rattle. Jera’s universe began to unwind. Threads threw exceptions and died. The Main thread, once so proud, caught the error and tried to log it, but even the logger needed memory to format the string. It failed too. Jera remembered the death
To the engineers upstairs, the JVM was just a process, a runtime environment executing bytecode. But inside the machine’s silicon heart, it was a universe. And at the center of that universe was , a sentient, silent god of memory and time. It knew that every object, every thread, every
The GC stalked across the Heap, a skeletal hand tracing references. It started from the —the static variables, the active stack frames. Then it walked the object graph.
There, in a quiet corner of the Tenured space, sat a HashMap inside a CacheManager singleton. The key was a UserSession object. The value was a List<AuditLog> . The problem? The UserSession objects never had their logout() method called. Each user who logged in left behind a session key, and the AuditLog list grew without bound.