Memory leak caused by Manage Old Data Administrative Monitor

Last Reviewed:2026-07-13()
1 minute readKnowledge base

Environment

  • CloudBees CI on modern cloud platforms - operations center

  • CloudBees CI on modern cloud platforms - managed controller

  • CloudBees CI on traditional platforms - operations center

  • CloudBees CI on traditional platforms - client controller

Related Issue(s)

Issue

A known memory leak can occur tied to the Manage Old Data administrative monitor (OldDataMonitor). This monitor warns you when you have data stored in an older format and/or unreadable data.

When this administrative monitor is active and enabled, it forces historical builds with old data to be loaded into memory, even if they were previously unloaded. If a large number of builds are reported to the monitor, this mass loading can cause significant memory consumption and lead to performance degradation or OutOfMemory (OOM) errors.

You can confirm if you are experiencing this issue by checking the admin-monitors.md file in a generated support bundle. The output will look similar to this:

Monitors
========
`OldData` _Manage Old Data_
--------------
  * Problematic object: `job_name/development/job_name-development/PR-1 #4`
    - CannotResolveClassException: com.cloudbees.jenkins.plugins.replication.builds.OwnerAction
  * Problematic object: `job_name/development/job_name-development/PR-101 #27`
    - CannotResolveClassException: libraryPath
▼

Resolution

This issue is resolved in CloudBees CI version 2.555.2.36753. The fix ensures build records are no longer incorrectly flagged and loaded into memory by the Manage Old Data monitor.

Workaround

If you are unable to upgrade immediately, you can mitigate the memory leak by disabling the administrative monitor:

  1. Navigate to Manage Jenkins > System > Administrative Monitors.

  2. Disable the Manage Old Data monitor.

  3. Restart the controller to clear the incorrectly loaded builds from memory.

This article is part of our Knowledge Base and is provided for guidance-based purposes only. The solutions or workarounds described here are not officially supported by CloudBees and may not be applicable in all environments. Use at your own discretion, and test changes in a safe environment before applying them to production systems.