Issue Summary

When a search is performed with issue-level security enabled and the user has many group memberships, Jira can use large amounts of memory leading to heap exhaustion.

Steps to Reproduce

Exact steps to replicate have not yet been fully determined, but this behaviour has been observed in a production Jira instance and confirmed by heap dump analysis to be related to metrics collection in Jira - the heap dump's dominator tree shows a large amount of memory stored by com.atlassian.jira.web.metrics.RequestLocalRfuMetricEvents as an array called RfuMetrics.

Expected Results

Jira should perform the search without excessive memory usage.

Actual Results

Jira uses excessive memory leading to heavy garbage collection activity and out of memory errors.

Workaround

Add the following dark feature flag to Jira to disable collection of the affected metrics: com.atlassian.jira.request.local.metrics.collector.disabled