Stack overload with Win-Explorer 8

abby normal · Dec 11, 2009, 07:19 AM

I get this message on my home page in Win Explorer 8: Message from Webpage Stack overflow at line 1217. I was using CNN.com as my home page. I changed my home page to something else to see if this message goes away. Since the message reads message from Webpage, is this MY problem? Can this be fixed, if it's in my PC? and HOW! I installed Windows7 monday, but I started to see this happen also on Vista home prem.

WxMan1 · Dec 16, 2009, 12:04 PM

This could be a javascript error or a server-side error. Usually javascript errors include the line number as a separate field, and not as part of the error message text. If it is a javascript error, then the line number can refer to the primary HTML, or to any externally referenced javascript files. If the error is displayed in the browser (as opposed to a pop-up message box), then it is a server-side error. Remember, javascript error messages never reference external files. Although they may reference the URL of the page you are viewing (primary resource), whether they show the URL of the primary resource, or not, is not related to where the error occurred. It is just a matter of how the browser wants to format its javascript error message box. IE has at least two different formats that it uses to report errors in a message box.

Either way, you should inspect the variables or identifiers being used on line 1217 of the relevant source file. You'll also want to eliminate duplicate functions and / or methods that are being called to do the same thing simultaneously. That's just bad. You get overzealous with the copy / paste thing and things like that can happen.

FYI: a stack over flow occurs because too many functions are being called with no returns. Usually that is because of recursive or circular function calls that have run amuk. If that doesn't get it straightened out, then you will probably need to post some relevant code.

FWIW: line numbers reported with a javascript error may be off by 1. So
determine which file it is referring to (primary HTML or external javascript file) and then check out reported line number as well as the lines immediately before and after that line number.

OBTW: forgot to mention, server-side scripting errors usually manifest themselves across browser platforms. So if it happens in any browser, its pretty foregone to be server-side scripting error. But if it only happens in one particular browser, its probably client-side script that's makin' the web-page cough up a bit-ball.

abby normal · Dec 20, 2009, 06:15 AM

Hi WxMan1,
Thank you for your help. I changed my home page in my browser, and problem has gone away. Again thank you!

Dec 11, 2009, 07:19 AM	#1
abby normal HardwareHeaven Junior Member Join Date: May 2009 Location: USA, VA. Posts: 52 Rep Power: 0 System Specs	Stack overload with Win-Explorer 8 I get this message on my home page in Win Explorer 8: Message from Webpage Stack overflow at line 1217. I was using CNN.com as my home page. I changed my home page to something else to see if this message goes away. Since the message reads message from Webpage, is this MY problem? Can this be fixed, if it's in my PC? and HOW! I installed Windows7 monday, but I started to see this happen also on Vista home prem. __________________ Abby Normal Laugh at your problems.... everyone else is.

Dec 16, 2009, 12:04 PM	#2
WxMan1 HardwareHeaven Lover Join Date: Dec 2007 Posts: 221 Rep Power: 40	Re: Stack overload with Win-Explorer 8 This could be a javascript error or a server-side error. Usually javascript errors include the line number as a separate field, and not as part of the error message text. If it is a javascript error, then the line number can refer to the primary HTML, or to any externally referenced javascript files. If the error is displayed in the browser (as opposed to a pop-up message box), then it is a server-side error. Remember, javascript error messages never reference external files. Although they may reference the URL of the page you are viewing (primary resource), whether they show the URL of the primary resource, or not, is not related to where the error occurred. It is just a matter of how the browser wants to format its javascript error message box. IE has at least two different formats that it uses to report errors in a message box. Either way, you should inspect the variables or identifiers being used on line 1217 of the relevant source file. You'll also want to eliminate duplicate functions and / or methods that are being called to do the same thing simultaneously. That's just bad. You get overzealous with the copy / paste thing and things like that can happen. FYI: a stack over flow occurs because too many functions are being called with no returns. Usually that is because of recursive or circular function calls that have run amuk. If that doesn't get it straightened out, then you will probably need to post some relevant code. FWIW: line numbers reported with a javascript error may be off by 1. So determine which file it is referring to (primary HTML or external javascript file) and then check out reported line number as well as the lines immediately before and after that line number. OBTW: forgot to mention, server-side scripting errors usually manifest themselves across browser platforms. So if it happens in any browser, its pretty foregone to be server-side scripting error. But if it only happens in one particular browser, its probably client-side script that's makin' the web-page cough up a bit-ball. Last edited by WxMan1; Dec 16, 2009 at 12:10 PM.

Dec 20, 2009, 06:15 AM	Thread Starter #3
abby normal HardwareHeaven Junior Member Join Date: May 2009 Location: USA, VA. Posts: 52 Rep Power: 0 System Specs	Re: Stack overload with Win-Explorer 8 Hi WxMan1, Thank you for your help. I changed my home page in my browser, and problem has gone away. Again thank you! __________________ Abby Normal Laugh at your problems.... everyone else is.