CloudBees Usage Analyzer Plugin causing heap memory pressure on monolith controllers

When a controller has the CloudBees Usage Analyzer Plugin plugin version 2.x, as well as a large number of jobs, for example more than 5,000 jobs on one controller (each of those jobs could have multiple branches if they are multibranch pipelines, as well as build history for each job), the instance can slow down and become unresponsive, and you will be unable to access the controllers web UI.

When reviewing Garbage Collection logs of the controller, you will see the typical pattern showing Consecutive Full GC: https://blog.ycrash.io/2021/10/15/interesting-garbage-collection-patterns/

When reviewing a heap dump (How to generate a heap dump?), you will notice that greater than 90% of heap memory is consumed by Plugin Usages Analyzer thread:

For example in Eclipse MAT, in the "Leak suspects" report you may see a leak suspect with:

And under the "Common Path to the Accumulation Point" you will see:

We recommend upgrading to CloudBees CI 2.440.3.7 or later, which contains:

Disable or uninstall the CloudBees Usage Analyzer Plugin plugin

When the plugin is disabled and you want to locate jobs that are using a specific plugin, for example the maven-plugin, you can run the following command which will list the job config.xml files for the jobs that use that plugin (note that this does not work for Pipeline steps, only plugins that save configuration settings to the jobs config.xml):