Hmm, not sdure I like the MS error description in this situation.
The only times I have seen that error from ASP were when I alloweda recursive funciton to recurse to deeply and when I had a set of to many objects linked together (which wre using recursive function calls to their children). SO basically what would happen is that I would make a single call, it would get pushed onto the stack, that funciton would call itslef (or a child object with the same function), the second function would get pushed to the stack while it was called a third time, etc. Every previous call dependned on the next call in order to complete so I ended up pushing to many waiting function onto the stack.
As an example, here is a function that theoretically would infinitely recurse, therefore each inner call causes the parent to be put on the stack. It overflows the stack quite quikly:
Code:
<%
Function BadRecurse(num)
Response.Write "Level " & num & "<br/>"
Response.Flush
BadRecurse = BadRecurse(num + 1)
End Function
Response.Write BadRecurse(1)
%>
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.