[Mono-bugs] [Bug 42757][Nor] Changed - Xsl Memory Leak

bugzilla-daemon@rocky.ximian.com bugzilla-daemon@rocky.ximian.com
Sun, 11 May 2003 01:08:39 -0400 (EDT)


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=42757

--- shadow/42757	Sat May 10 22:02:06 2003
+++ shadow/42757.tmp.16744	Sun May 11 01:08:39 2003
@@ -1,14 +1,14 @@
 Bug#: 42757
 Product: Mono/Class Libraries
 Version: unspecified
 OS: All
 OS Details: 
-Status: NEW   
-Resolution: 
-Severity: 
+Status: RESOLVED   
+Resolution: NOTABUG
+Severity: Unknown
 Priority: Normal
 Component: System.XML
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: bmaurer@users.sf.net               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
@@ -86,6 +86,23 @@
 
 Expected Results:
 Results shown with minimal memory usage.
 
 How often does this happen? 
 Always.
+
+------- Additional Comments From gonzalo@ximian.com  2003-05-11 01:08 -------
+Try moving the first 3 lines of the loop out of there:
+
+	XslTransform xslt = new XslTransform ();
+	XPathDocument xml = new XPathDocument (XslFile);
+	xslt.Load (XmlFile);
+			
+	for (int i = 0; i < 50000; i++)
+		xslt.Transform (xml, null, Console.Out);
+
+
+Run it inside memprof or something similar. I can see about 1200kb
+used and it does not move from there.
+
+Running your test case don't stop increasing memory usage, but memprof
+does not display any leak. I bet it's related to memory fragmentation.