CollectingLRUCache can grow large due to fUseStats which can cause heap memory pressureDescriptionThe memory consumption is caused by a specific cache "syscache_jelly_script" which also had an internal map that stores usage statistics based on unique cache keys. That cache was disabled for many years ago by setting the size to 0, so we are not actually storing anything in the cache or using it at all for any performance improvement. However, the underlying map which stores usage statistics was still recording the unique keys that we were trying to put into the cache. Typically, the memory consumption of this would be small (less than 5 MB), however in some instances with many languages, roles, domains, and unique users on a node the count of unique keys can be very large causing this internal usage statistics to consume enough memory to cause performance issues.Steps to Reproduce Typically a heap dump needs to be taken to identify the issue. To reproduce things getting put into the fUseStats you can view multiple forms (incident, change, cmdb, etc) as multiple users who have different languages, roles, domains, etc. WorkaroundWe already have a better way to fully disable the cache, which will prevent any memory from being consumed by the usage statistics, by including "syscache_jelly_script" in the "glide.cacheman.disabled_cache_catalogs" property. If you do not already have the property on your instance then you can create a new one. Name: glide.cacheman.disabled_cache_catalogsValue: syscache_jelly_script If you already have the property then you can just add the "syscache_jelly_script" to the value (comma seperated) like this: Name: glide.cacheman.disabled_cache_catalogs Value: some_other_caches,syscache_jelly_script Related Problem: PRB1804575