Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>A stack overflow occurs when your stack size reaches the defined limit and no more elements can be placed on the stack. The default stack size in Windows is normally 1 MB and has nothing to do with the total memory available to a process (therefore looking at the memory used by w3wp.exe makes not much sense in your case).</p> <p>It is possible to increase the stack size of an executable. From a Visual Studio command prompt you can issue</p> <pre><code>editbin /STACK:4000000 w3wp.exe </code></pre> <p>to increase the stack size to 4 MB.</p> <p>However, it could also be the case that the stack overflow is caused by a problem in the code (typically an <strong>infinite recursion</strong>) which would only occur when hosted as a WCF service.</p> <p>To trace this problem down, you need to find out where the recursion occurs. If you can't get a stack trace intensive logging will help you here.</p> <p><strong>UPDATE</strong></p> <p>As it seems, w3wp.exe does not use Window's default stack size of 1 MB but uses only 256 kB (see also this <a href="http://support.microsoft.com/kb/932909" rel="nofollow noreferrer">knowledge base article</a>):</p> <pre><code>dumpbin /HEADERS c:\windows\system32\inetsrv\w3wp.exe </code></pre> <p>prints: </p> <blockquote> <pre><code>[...] OPTIONAL HEADER VALUES [...] 40000 size of stack reserve </code></pre> </blockquote> <p>A <a href="http://blogs.msdn.com/tom/archive/2008/03/31/stack-sizes-in-iis-affects-asp-net.aspx" rel="nofollow noreferrer">blog post</a> suggest to patch w3wp.exe using <code>editbin</code> as described above.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload