[Mono-dev] Debugging Out of Memory Exceptions

Bryan Murphy bmurphy1976 at gmail.com
Tue Dec 29 14:34:31 EST 2009

We have a long running process that processes many many small messages and
infrequent multi gig files.  Occasionally, an OutOfMemoryException is
thrown.  When this happens, the process gets into a funky state and nothing
works properly until I restart it.  I'm not that experienced debugging
memory issues on mono on linux, so I could use some help.

1. Can I have a mono process sigseg and exit completely when an
OutOfMemoryException is thrown?

2. Can I automatically take a memory snapshot only when OutOfMemoryException
is thrown for later analysis?

3. Any other advice on how I can find the culprit when it happens only
occasionally in the production environment usually when nobody is looking
and the process has been running for a few days?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.ximian.com/pipermail/mono-devel-list/attachments/20091229/0ea536d3/attachment.html 

More information about the Mono-devel-list mailing list