[Mono-bugs] [Bug 435549] New: Memory leak with Response.Cache.SetCacheability( HttpCacheability.Public);

bugzilla_noreply at novell.com bugzilla_noreply at novell.com
Wed Oct 15 03:44:52 EDT 2008


https://bugzilla.novell.com/show_bug.cgi?id=435549


           Summary: Memory leak with
                    Response.Cache.SetCacheability(HttpCacheability.Public);
           Product: Mono: Class Libraries
           Version: 2.0
          Platform: Other
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Sys.Web
        AssignedTo: mhabersack at novell.com
        ReportedBy: informatique.internet at fiducial.fr
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---


I've found a leak in ASP.NET on mono.

The leak is present on mono 2.0 and 1.9.1 but not on mono 1.2.6, but i don't
know if it is present for svn version

The test is very simple: try this aspx :

<%@ Page Language="C#"  EnableSessionState="False" enableViewState="False" %>
<script runat="server">
        protected override void OnLoad(System.EventArgs e)
        {
                        Response.Clear();
                       
Response.Cache.SetCacheability(HttpCacheability.Public);
                        Response.End();
        }
</script>


run xsp on it

and run ab2 (apache tester)
 /usr/sbin/ab2 -c 5 -n 10000 http://localhost:8080/

and you'll see RSS memory growing and growing...

Note : if you put Response.Cache.SetCacheability(HttpCacheability.NoCache);
instead it doesn't leak

Note : According to MSDN SetCacheability should only add correct headers for
enabling/disabling client side cache... this shouldn't affect any server side
caching...

Note: this is reproducible with xsp and mod_mono

Note: this prevent our CMS (http://www.fiducial.biz) to work with mono 2.0

Note: if you find the solution could you backport to 2.0 branch


Regards,


-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.


More information about the mono-bugs mailing list