Issue Summary

Consecutive Issue navigation/search impacts performance (possible memory leak)

Steps to reproduce

1. Perform an issue search
2. Click on one of the issues that were result of the search
3. The top right of the View Issue screen has the navigation option to move back and forth through the issue search result, click on it:
   

Expected results

The action is done, the issue is scrolled to the next/previous and there is no performance impact.

Actual results

1. After each click to change the issue (and the issue is actually loaded), browser's memory increases.
2. This increase seem to be higher on each subsequent issue that you scroll through
3. After 30-50 issues, each time you navigate through an issue, about 60m+ increases on the memory usage of the Google Chrome's tab
4. It seems like the browser identifies the whole process as one single request. You can noticed through the .HAR file that it is logged as a single request that reaches multiple issues.

This will go on until the whole browser ends up crashing.
Tested on Google Chrome version 62.0.3202.89 and Firefox 56.0.2.

Workaround

Opening each issue on new tabs or windows instead of using the top right arrows on the Issue Navigator.