Solved

Firefox 2.0.0.14 Memory Leak when making any AJAX calls

Posted on 2008-06-10
5
577 Views
Last Modified: 2013-12-07
Very simply, if you continue to make AJAX calls in FireFox, and watch the memory usage in task manager, it constantly grows and if left over night may crash the browser.

I need the constant polling because we are monitoring data that needs to constantly be updating the screen.

Does anyone know how to work around or fix this memory leak?

Here's a simple page doing nothing but AJAX requests in an infinite loop (you can see the request using FireBug or some other http viewer)

http://www.cyberena.com/Production/ajaxtest/jqcall.html

0
Comment
Question by:cyberena
  • 3
  • 2
5 Comments
 
LVL 18

Expert Comment

by:ChetOS82
ID: 21753315
I don't think this is a memory leak in Firefox, because it jQuery uses Firefox's XmlHttpRequest object.  I have been using that object for years and (when used right) never had a problem.

What happens if you point your success callback to a function other than the calling function?  If you need it to process in a loop, then have the callback function call the "theCall" function again.

Also, jQuery provides $.get() which might be better suited for your needs.
0
 

Author Comment

by:cyberena
ID: 21753758
Hello,

I have used JQuery and Prototype and my own engine I wrote before those open sources even existed for AJAX calls and all three produce the same results no  matter if the callback function is hitting itself or another function.

A possible reason you have not seen it is perhaps you are not polling data as often as I am in the example I provided which is every 50ms plus or minas for over night or longer periods of time since the application I am writing monitors robots.

I believe if you try to do an infinite request loop, and watch the memory in task manager, you can also reproduce the problem in FF 2.

It seems FF 3 beta has resolved this problem, and no leak in IE either.  But I am hoping to find a workaround for now for FF 2 since many people use FF2 today.
0
 

Author Comment

by:cyberena
ID: 21753770
One more thing to note, the memory leak is apparent after just a few minutes of inifinite looping, you dont have to wait overnight to see the memory grow.
0
 
LVL 18

Accepted Solution

by:
ChetOS82 earned 500 total points
ID: 21753909
I figured out the problem (on my machine at least).  I turned off the XMLHttpRequest logging in Firebug (by going to the Console tab, clicking on Options and unselecting "Show XMLHttpRequest").  I restarted Firefox and monitored the memory usage.  It held steady (up or down <1K).  I verified that requests were being made using WireShark.

I then opened Firebug back up and asked it to show the XMLHttpRequests and Firefox's memory started increasing.
0
 

Author Closing Comment

by:cyberena
ID: 31465807
Thank you, unfortunately all of my systems I dev on use FireBug, I never thought of the memory increase being due to FireBugs logging but it makes sense.  
0

Featured Post

Do You Know the 4 Main Threat Actor Types?

Do you know the main threat actor types? Most attackers fall into one of four categories, each with their own favored tactics, techniques, and procedures.

Join & Write a Comment

Several part series to implement Internet Explorer 11 Enterprise Mode
Boost your ability to deliver ambitious and competitive web apps by choosing the right JavaScript framework to best suit your project’s needs.
This video teaches users how to migrate an existing Wordpress website to a new domain.
The viewer will learn the basics of jQuery, including how to invoke it on a web page. Reference your jQuery libraries: (CODE) Include your new external js/jQuery file: (CODE) Write your first lines of code to setup your site for jQuery.: (CODE)

707 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

19 Experts available now in Live!

Get 1:1 Help Now