Skip to main content

Bug Tracker

Side navigation

#8874 closed bug (duplicate)

Opened April 14, 2011 01:55PM UTC

Closed April 18, 2011 02:56PM UTC

Last modified April 27, 2011 09:22PM UTC

IE8 Memory leak

Reported by: jason@cheerleading.com Owned by: jason@cheerleading.com
Priority: low Milestone: 1.next
Component: global Version: 1.5.2
Keywords: Cc:
Blocked by: Blocking:
Description

Upon setting our companies website from 1.4.4 to 1.5.2 20-30 employees started complaining within 2-3 hours getting "out of memory error on line ##" only in IE8. As soon as I put the site back to 1.4.4 all the complaints went away.

There isn't any heavy jQuery on the site, but most of these people probably had the site sitting in the background for a while before it happened.

Attachments (0)
Change History (5)

Changed April 14, 2011 02:17PM UTC by timmywil comment:1

component: unfiledglobal
owner: → jason@cheerleading.com
priority: undecidedlow
status: newpending

Thanks for taking the time to contribute to the jQuery project! More information is needed to assess your ticket. It would be helpful if you could narrow down the source of the leak you are experiencing or provide a test case on http://jsfiddle.net to ensure it is an issue with jQuery.

Changed April 18, 2011 09:34AM UTC by petnys comment:2

We have had similar problems with jQuery 1.5 and IE, so we also downgraded to 1.4.4. A very simple test case is to include jQuery 1.5 in a page that is viewed inside a frame/iframe. Each time the frame is reloaded the memory usage for IE increases with a couple of MBs. Memory is only returned when the entire browser window is reloaded or closed. Changing the jQuery version to 1.4.4 removes the memory issue.

Changed April 18, 2011 02:56PM UTC by timmywil comment:3

resolution: → duplicate
status: pendingclosed

Changed April 18, 2011 02:56PM UTC by timmywil comment:4

Duplicate of #8863.

Changed April 27, 2011 09:22PM UTC by dossy comment:5

Confirmed that jQuery 1.5.2 is resulting in an "out of memory" error on the HP t5510 thin client running WinCE .NET 4.2 and IE6. Reverting to jQuery 1.4.4 seems to solve the problem - thanks.