My Jenkins controller has high memory usage due to Support Core plugin memory leak

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

Issue

The JVM heap usage reaches critical levels (95% or higher), causing garbage collection thrashing. The controller refreshes frequently or becomes unavailable, and OutOfMemoryError conditions may occur.

Environment

Resolution

This issue is tracked as a bug, and will be fixed in a future release of CloudBees CI. This article will be updated when the fix is available.

Workaround

Disable the specific Support Core extensions that generate command-stats.md files using the Extension Filter plugin:

  1. Install the Extension Filter plugin from the Update Center.

  2. Navigate to Manage Jenkins  System.

  3. Find the Extension Filter section.

  4. Add three Exclusions using the following Java class names:

    • com.cloudbees.jenkins.support.impl.SlaveCommandStatistics

    • com.cloudbees.jenkins.support.impl.SlaveCommandStatistics$ComputerListenerImpl

    • com.cloudbees.jenkins.support.impl.SlaveCommandStatistics$NodeListenerImpl

  5. Save the configuration.

  6. Restart the controller.

  7. Monitor heap usage to confirm the memory leak has stopped.

This workaround disables Agent Command Statistics collection in support bundles. This functionality will remain disabled until the Support Core plugin is fixed and the extensions are re-enabled.

Tested product/plugin versions

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.