I regularly get the message "Stack overflow at line 0" What's the cure? Thanks in advance, Harry
B> A stack is a section of memory where a program stores its variables, calculations, option states and program parameters. When started, a program is allocated some memory to use for the stack; a stack overflow happens when a program exceeds its allocation. The offending program may attempt to write into adjacent memory sections, causing conflicts with other programs. Stack overflows are common with Java, C++, Perl and other runtime environments, which assist in running programs. A stack overflow at line 0 indicates that the offending program tripped up from the start; however, stack overflows can occur on any line number.
Click "Start," "Control Panel, then "Internet Options." Click on the "Advanced" tab. Check "Disable Script Debugging (IE)" and "Disable Script Debugging (Other)" under the "Browsing" options. Uncheck "Display a notification about every script error." Check "Enable Automatic Crash recovery." Click "OK." Download and install a Java update from the Java website. http://www.java.com/en/download/manual.jsp Download and install a Windows update. Hope this helps.
SOURCE: Computer pop up
IE:
stack overflow at line: 0
Today, I noticed the following issue
(IE only, of course). Running a page that does some comet (via “XHR GET”
for long-polling), I got the following warning: “stack overflow at
line: 0′ and the application stopped working…
I did some google-searches and found some “hints” that said I should
disable my third-party tools for IE etc. That sounds strange…
In fact the problem was the odd cache behavior of the IE. The XML
(from the “long-polling servlet”) was cached and its JS was executed;
also the application itself started the polling too, so I (no IE) ran
into this odd issue…
Changing the server-side code – that is responsible to render the XML
– to have no cache rules (e.g.”Cache-Control”:”no-cache”) did the
trick. It worked again. Of course, on your “comet output” you
potentially don’t want cache to be present…
So fixing the cache solved the issue. There was no need to disable
Norton or any other third-party tool… 
Testimonial: "Very helpful. Thanks for the information."
570 views
Usually answered in minutes!
×