Why is there a memory / stack overflow problem in IE?

  • Profile Image
    Asked on April 05, 2011 at 05:51 PM

    I'm using JotForm on a website -- the code is embedded, not in an iframe, for stying reasons. 


    But in internet explorer, I get consistent memory errors... is there a way around this? 






    *edit - page was fixed when I removed some of the linked JS files. I'm now using a separate jQuery form validator, but am happy with the forms. 

  • Profile Image
    Answered on April 06, 2011 at 02:43 AM


    First of all let me congratulate you on a wonderful looking form. It is one of the best I've seen from our users, so far. Anyway, I wasn't able to replicate your problem in IE8 - I did not get a stack overflow message but I see an error alert at the bottom of the browser window.

    Upon checking the error, it seems that the problem is caused by the Google Maps plugin for jquery in your page.

    I also checked the other pages of your site and I found out that even the pages that do not have Jotform forms in them still gets the same error.



    Obviously, it looks like the error has nothing to do with Jotform but with the Google Map plugin instead. Try disabling that plugin and see if it helps.

    Get back to us if you have further questions.


  • Profile Image
    Answered on April 06, 2011 at 02:51 AM


    Not sure about that problem but somehow I read somewhere then that it has something to do with the so called memory leak problem with Internet Explorer as well.

    To get around this issue, you will have to do this:

    Add this script code in your header:

    Add this script code in your header:

    <script type="text/javascript">

    function noError(){return true;}
    window.onerror = noError;


    This script will eliminate the alert although this does not necessarily solve the problem with IE.  And this will also eliminate all alerts actually if you have other scripts running on your webpage that requires the alert window to show up.

    Hope this helps.

    But I would suggest that you try out how to find a fix from what Neil saw before resorting to my solution.