Major memory leak in IE10's Javascript setInterval implementation - by Sebastian Mueller

Status : 

  Fixed<br /><br />
		This item has been fixed in the current or upcoming version of this product.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

ID 783448 Comments
Status Closed Workarounds
Type Bug Repros 1
Opened 4/11/2013 7:30:15 AM
Access Restriction Public


During testing we found a major memory leak in IE 10 implementation of setInterval.
Basically any function that will ever be passed to setInterval does not seem to become eligible for garbage collection. If the function captures other (temporary) javascript objects in its closure this can quickly become a major memory leak. In our test case this results in IE taking up half a gigabyte of memory withing seconds, whereas other browsers (IE9, Chr., FF.) all idle at far less than a hundred megabytes and finally release the memory.
With memory not being released some more modern single page web apps may quickly cause IE eat up so much memory that it becomes barely unusable.
Sign in to post a comment.
Posted by Alexandr Abramov on 11/24/2013 at 2:07 AM
We have installed IE11 and saw that the problem still exists.
We have Win7 OS. does it matter?

Posted by Microsoft on 6/27/2013 at 1:01 PM
Thank you for your feedback.

We have released a new preview version of Internet Explorer which is included with Windows 8.1 available from the following location:
During our testing we are no longer able to reproduce the issue using Internet Explorer 11 please verify you are still experiencing the reported problem in this new release. If the issue continues please reopen this connect feedback item and provide additional details that will help us continue our investigation.

Best regards,

The Internet Explorer Team
Posted by Microsoft on 4/16/2013 at 2:59 PM
Thank you for your feedback. We will be investigating this issue further.

Best regards,

The Internet Explorer Team