Summary

The issue navigator leaks memory in the client-side when browsing through the issue results in an issue search. This happens in both list view and details view, and has been tested in google chrome

Environment

(Optional - If Applicable)

• Google Chrome.

Steps to Reproduce

1. Execute a JQL Query with a significant number of total results (for example, 1000).
2. Open Developer Tools --> Timeline - Check memory and Start Recording.
3. Start browsing through the issues in the list (use j/k in list view / using the up-down arrows should be enough in details view).
4. After you have done this for a number of issues (for example, 20), stop recording in the Timeline.
5. BUG Notice the graph on memory consumption and how it keeps creeping up without memory being reclaimed.

Expected Results

Memory usage does not keep increasing as you browse through issues. The allocated memory used when you go from one issue to another is reclaimed.

Actual Results

Memory usage keeps increasing as you browse through all the issues in your results potentially leading to slugginess in the client.

Workaround

Close the tab / Chrome and navigate to the page again in a new tab.

Original Description

When leaving JIRA open in Chrome for an extended period of time, Chrome will eventually grow to consume a large percentage of the RAM on my machine. As much as 50% of available RAM will be set for that process in Chrome (not the only chrome process).

Ending this chrome task will close out only JIRA tabs, indicating that JIRA is causing the memory leak.