StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POAsp.net crashing in mscorlib
text
Body
copied!<p>This is related to <a href="https://stackoverflow.com/questions/1023562/asp-net-caching-and-w3p-memory-usage">another question of mine</a></p> <p>After eliminating the obvious (or so I thought) and biggest memory consumer (images in asp.net cache), not much has changed. We use Enterprise Library Exception Handling in this web (don't know why, but we do) and these exceptions do not get logged. Just for the record, server has 4 GB of memory so I do not think that physical memory is the problem. </p> <p>Here's what happens, according to event log:</p> <p>First I get this from a page (rarely from a same page twice):</p> <pre><code>Exception information: Exception type: Exception Exception message: mscorlib - Exception of type 'System.OutOfMemoryException' was thrown. </code></pre> <p>Then this:</p> <pre><code>Description: An unhandled exception occurred and the process was terminated. Application ID: /LM/W3SVC/672222825/Root Process ID: 1544 Exception: System.OutOfMemoryException Message: Exception of type 'System.OutOfMemoryException' was thrown. StackTrace: at System.Threading.ExecutionContext.CreateCopy() at System.Threading._TimerCallback.PerformTimerCallback(Object state) </code></pre> <p>My question is this: how do I use a profiler to see what is causing the crash? I've tried two profilers - .net memory profiler and dotTrace from JetBrains. Memory profiling doesn't really give me anything useful, except that I have a lot of strings. Performance profiling also isn't helping because execution times of functions are all fine and dandy. If this error happens while the profiler is running, it just stops profiling - I'm probably using it wrong. </p> <p>p.s. Sorry for the formmating, did the best I could. </p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

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