none
Where to start finding source of Stack Overflow Exception ? RRS feed

  • Question

  • I am getting the following error on a Windows 2008 R2 server using .NET 4.0

    Problem Event Name: CLR20r3

      Problem Signature 01: myprogram.exe

      Problem Signature 02: 3.0.0.0

      Problem Signature 03: 56e18eeb

      Problem Signature 04: wimwanan

      Problem Signature 05: 0.0.0.0

      Problem Signature 06: 57905dff

      Problem Signature 07: 1a

      Problem Signature 08: 0

      Problem Signature 09: System.StackOverflowException

    Thanks for any ideas

    Tom


    MisterT99


    • Edited by Mister T99 Thursday, July 21, 2016 2:01 PM
    Thursday, July 21, 2016 2:01 PM

Answers

  • You will want a lot more of the stack than that, stack overflows are rarely ever thrown near the bug that caused them.

    Look for a repeating pattern in the methods on the stack, one of them is likely to be the culprit.

    Raymond Chan did a good write up on this some time ago. (the blog post focuses on native code, but the principals are the same)

    https://blogs.msdn.microsoft.com/oldnewthing/20090107-00/?p=19573

    Thursday, July 21, 2016 9:49 PM

All replies

  • Hi,

    you should ask the developer of the application. That is a problem of the application itself and not a problem of th runtime.

    A reason for this exception could be some problem with a recursion that was implemented. (Stack overflow means, that there wasn't enough space on the stack. The stack is some memory which is used to store data on function calls. When a function is called, the return address and all parameters will be added to the stack. The function will then add local variables on the stack. Once the function call ends, everything put on the stack is taken of the stack and then the execution continues at the return address.)

    With kind regards,

    Konrad

    Thursday, July 21, 2016 2:52 PM
  • Konrad, I am the developer.  This code has been running for years with no errors.

    I suspect it is some kind of problem with the data being changed.

    Thanks


    MisterT99

    Thursday, July 21, 2016 3:51 PM
  • >Konrad, I am the developer. 

    Then capture a stack trace.

    >This code has been running for years with no errors. I suspect it is some kind of problem with the data being changed.

    Yep.  Lots of bugs only appear with certain data.

    David


    David http://blogs.msdn.com/b/dbrowne/

    Thursday, July 21, 2016 4:02 PM
  • David,  Thanks for your reply.

    I found some data that caused the stack overflow error.  I was prompted to debug, so I got into the VS 2012 debug mode.

    Got these messages:

       System.StackOverflowException occurred in wimwanan

       Cannot debug external code

    What is wimwanan ?  I did a search and nothing was returned.

    What is the next step ?

    Many thanks

    Tom


    MisterT99

    Thursday, July 21, 2016 6:20 PM
  • You will want a lot more of the stack than that, stack overflows are rarely ever thrown near the bug that caused them.

    Look for a repeating pattern in the methods on the stack, one of them is likely to be the culprit.

    Raymond Chan did a good write up on this some time ago. (the blog post focuses on native code, but the principals are the same)

    https://blogs.msdn.microsoft.com/oldnewthing/20090107-00/?p=19573

    Thursday, July 21, 2016 9:49 PM
  • Brian, thanks for taking time to reply to this question.

    I will read that article.

    Thanks

    Tom


    MisterT99

    Thursday, July 21, 2016 9:52 PM
  • I was able to duplicate the error using some data from one customer.  However, further tests using the same data did not produce an error.

    Will have to delay further testing until I can duplicate the problem again.

    Thanks for everyone's help

    Tom


    MisterT99

    Friday, July 22, 2016 12:00 PM