The RMNodeImpl.updatedExistContainers was not removing entries related to containers that had already finished execution. As the number of finished containers increased, these objects stayed in memory indefinitely, which gradually consumed more memory, ultimately causing the system to run out of memory (OOM).