In Geneva and later releases running in Internet Explorer 11, the iexplore.exe process consumes more and more memory with each page load, constituting a memory leak. The memory leak stems from the asynchronous message bus that powers many live features in UI16. When this feature is used on pages containing iframes, there is a bug in Internet Explorer 11 that causes the browser to maintain unnecessary information in memory. The fix works around the Internet Explorer 11 memory leak by handling the message bus connections differently.
Steps to Reproduce
- Open an instance using Internet Explorer 11.
- Open the task manager to observe Internet Explorer memory usage.
- Navigate to an incident form.
- Use the arrow keys on the top right to move between incident forms.
Note that Internet Explorer memory usage continues to climb by 10 - 20 megabytes per page. If you continue to navigate between pages, Internet Explorer crashes after going through a large number of forms.
Note: This PRB alleviates all IE11 browser memory issues related to iFrames outside of List v3 for Helsinki (Istanbul does not have this memory leak issue in List v3). If you have List v3 enabled in Helsinki builds, you will experience a varying degree of a memory leak in the IE11.
This memory leak is specific to IE11. If you are able to switch to a different browser this resolves the issue. If not, you need to upgrade to one of the versions listed in the Fixed In section below.
Related Problem: PRB713556