[Mono-bugs] [Bug 66751][Blo] Changed - [PATCH] XSP Leak

[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 bmaurer@users.sf.net.

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

--- shadow/66751	2004-09-23 23:00:47.000000000 -0400
+++ shadow/66751.tmp.25169	2004-09-23 23:04:13.000000000 -0400
@@ -1,23 +1,23 @@
 Bug#: 66751
-Product: Mono: Runtime
+Product: Mono: Class Libraries
 Version: unspecified
 OS: unknown
 OS Details: 
 Status: NEW   
 Resolution: 
 Severity: Unknown
 Priority: Blocker
-Component: misc
-AssignedTo: mono-bugs@ximian.com                            
+Component: Sys.Web
+AssignedTo: bmaurer@users.sf.net                            
 ReportedBy: bmaurer@users.sf.net               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
 URL: 
 Cc: 
-Summary: XSP Leak
+Summary: [PATCH] XSP Leak
 
 Right now, XSP is leaking under stress. Try the following:
 
 run xsp in the sample directory share/doc/xsp/test.
 
 With openload, run
@@ -50,6 +50,19 @@
 leaked per request.
 
 ------- Additional Comments From bmaurer@users.sf.net  2004-09-23 23:00 -------
 Created an attachment (id=11295)
 I fixed the bug :-D
 
+
+------- Additional Comments From bmaurer@users.sf.net  2004-09-23 23:04 -------
+The attached patch fixes this leak.
+
+The problem was that we were adding stuff to the timeout manager too
+many times, and only removing it once. The net affect was that the
+HttpContexts were kept forever. As a result, the streams etc were held
+by the GC.
+
+The new System.Web just allowed me to server 200k pages. Before, I
+died with 10k.
+
+Gonzalo -- please approve.