I have a big site running several subdomains all off the same set of code. All happily trucking along for the last few years For one section I needed to update prototype.js which is preloaded on all pages in whether its needed or not. With the update I started getting stackoverflow errors which I researched and managed to control in everything but good old IE. the first round of errors (which were handled quietly by FF etc) were fixed by putting a typeof query before the offending line. With this one it makes no difference. Its inappropriate to change to jquery - so how can I resolve this? Any ideas?
Stack overflows are typically if you have stuff that drops into looping sub-routines. Like if you have a function that calls itself. Even if it's not an infinite loop, browsers are going to have limits on how many iterations they can handle/track at once. Like it probably wouldn't be a great idea to call a function that calls itself before returning from the function (even if you had some counter/logic that limited it to 10,000 times). Child sub-routines/functions that have 10,000 levels of descendants would just be no bueno. That might not be the issue here, but that's the most common reason for stack overflows (running out of sub-function pointers).
Have turned it off for now, all I was really doing was caching the script so later pages load quicker . It should not have been running in the first place. Odd. Didn't happen before the upgrade.