[Mono-aspnet-list] Memory Leak in Generic Handler

Niknak nick.pateman at certivox.com
Fri Dec 7 14:09:06 UTC 2012

Hi there,

I'm using a Generic Handler in my mono application, something which I have
done many times in Windows ASP.NET.  Unfortunately I seem to be experiencing
a rather strange issue with mono that is seemingly causing a memory leak (my
Peak Working Set increases indefinitely until the application crashes with
an Out of Memory exception).

I thought maybe I was leaving some handles open but I'm pretty sure that I
am not (afaik).  I have several payload types being uploaded, the most
noticeable is obviously large amounts of binary data, as the working set
increases much quicker.  I have removed the majority of my code so that it
still functions but just ignores the binary data, unfortunately the leak
still persists.

Is there anything I should know about mono generic asp.net handlers that
differs from Windows?  The code left in my binary upload path, effectively
just does the following,

1.  Parses the URI into its components for RESTful use
2.  Returns a  JSON success blob
3.  Ends the request

Surely my working set shouldn't increase under this circumstance, I would
understand if I were streaming the binary data elsewhere from the request,
but it's being ignored for these requests.

Should I be disposing of the request stream manually?

I'll continue to plug away at it, but any help would be much appreciated!


View this message in context: http://mono.1490590.n4.nabble.com/Memory-Leak-in-Generic-Handler-tp4657696.html
Sent from the Mono - ASP.NET mailing list archive at Nabble.com.

More information about the Mono-aspnet-list mailing list