We have an appliaction that is causing the IIS to brake down on our production system, on the development system this does not seem to occure. We do not quite know what exactly is causing this but I've done some debugging via memorydumps. The problem is that the error is not show in a yellow screen of death, but the IIS simply stops the process and restarts.
By using the Adplus script in the microsoft debugging tool kit i've manged to create memory dumps at the time the exception is thown.
Then analysing the memorydump with windbg i've come up with the following stack trace:
StackOverflowException causes IIS to crash
Hi mighty everyone.
We have an appliaction that is causing the IIS to brake down on our production system, on the development system this does not seem to occure. We do not quite know what exactly is causing this but I've done some debugging via memorydumps. The problem is that the error is not show in a yellow screen of death, but the IIS simply stops the process and restarts.
By using the Adplus script in the microsoft debugging tool kit i've manged to create memory dumps at the time the exception is thown.
Then analysing the memorydump with windbg i've come up with the following stack trace:
The question is of course what is causing the exception. It seems to be related to XSLT somehow but I cant figure out where the culprit is.
Any input is appreciated.
We found the problem!
The problem was caused by a recursive xsl:template. This template was quite large and after 4 calls the stack was filled up.
The substringbefore() methods basicly was the one causing the drop that spilled the cup.
Bonus info: the stack size of a asp.net thread is 256kb
is working on a reply...