[Mono-bugs] [Bug 56038][Nor] Changed - Memory leak in the outputcache of a page.

[bugzilla-daemon@bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by gonzalo@ximian.com.

http://bugzilla.ximian.com/show_bug.cgi?id=56038

--- shadow/56038	2004-06-23 08:24:32.000000000 -0400
+++ shadow/56038.tmp.16517	2004-06-23 15:44:09.000000000 -0400
@@ -1,13 +1,13 @@
 Bug#: 56038
 Product: Mono: Class Libraries
 Version: unspecified
 OS: unknown
 OS Details: 
-Status: NEW   
-Resolution: 
+Status: RESOLVED   
+Resolution: NOTABUG
 Severity: Unknown
 Priority: Normal
 Component: Sys.Web
 AssignedTo: gonzalo@ximian.com                            
 ReportedBy: ya@slamail.org               
 QAContact: mono-bugs@ximian.com
@@ -60,6 +60,31 @@
 
 Always.
 
 Additional Information:
 
 none.
+
+------- Additional Comments From gonzalo@ximian.com  2004-06-23 15:44 -------
+If you add this line to the beginning of method OnRawResponseRemoved
+in System.Web.Caching/OutputCacheModule.cs file:
+Console.WriteLine ("removed: {0} {1} {2}", key, value, reason);
+
+and execute this script:
+while [ 1 -eq 1 ]; do a=`expr $a + 1`; wget
+http://127.0.0.1:8080/oc.aspx?id=$a; sleep 1; done
+
+after 1 minute (+- a few seconds) you'll get on the terminal running
+xsp things like:
+/oc.aspx
+METHOD:GET
+VP:id=1
+ System.Web.Caching.CachedRawResponse Expired
+removed: CachedRawResponse
+/oc.aspx
+METHOD:GET
+VP:id=2
+ System.Web.Caching.CachedRawResponse Expired
+removed: CachedRawResponse
+
+So the "leak" is not because old data is not being disposed, but
+because new data is inserted more quickly than removed.