Skip to main content

Bug Tracker

Side navigation

#8087 closed bug (invalid)

Opened January 28, 2011 11:30PM UTC

Closed January 28, 2011 11:44PM UTC

Last modified January 29, 2011 05:24PM UTC

Memory leak in IE8 when using ajax with jQuery.js.1.4.4.js package

Reported by: anonymous Owned by:
Priority: low Milestone: 1.next
Component: ajax Version: 1.4.4
Keywords: Cc:
Blocked by: Blocking:
Description

Doing an ajax post with 3 seconds. but sometimes is a memory leak. How can I fix it. I found the solution for the Jquery.1.4.2.js package. but Is there any solution for

jQuery.1.4.4.js about memory leak.(stack overflow at line bla bla).

Attachments (0)
Change History (4)

Changed January 28, 2011 11:44PM UTC by ajpiano comment:1

resolution: → invalid
status: newclosed

This is not a valid bug. Please follow the bug reporting guidlines before filing. Thank you.

Changed January 28, 2011 11:57PM UTC by jitter comment:2

component: unfiledajax
priority: undecidedlow

As you can't seem to provide more information or a test case to pinpoint a potential leak we can't take any further steps to fix this. You may want to try out the current 1.5rc1 release of jQuery which includes a major ajax-rewrite and check if the leak still happens there for you.


I'm only aware of one thing that caused ajax leaks in IE. The custom abort function jQuery used for the ajax-functionality. This has since been fixed. If you suspect this could be the culprit in your case also and you absolutely need this fixed in 1.4.4 you may want to look at this commit which fixed the abort-leak in IE. But applying this yourself and using a modified jQuery version is something I wouldn't advise you to do.


Please report back once you have determined if using 1.5rc1 fixes the leak for you.

Changed January 29, 2011 02:39PM UTC by anonymous comment:3

ie9 have a problem when i use 1.5rc1. i have to solve in 1.4.4.js. another solution you have??

Changed January 29, 2011 05:24PM UTC by jitter comment:4

Replying to [comment:3 anonymous]:

ie9 have a problem when i use 1.5rc1. i have to solve in 1.4.4.js. another solution you have??

What problem? How did it get resolved by using 1.4.4? For what should we have a solution? --> How to report bugs