[Mono-bugs] [Bug 65406][Maj] Changed - TheadPool leaks RAM

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Tue, 7 Sep 2004 11:01:35 -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 lupus@ximian.com.


--- shadow/65406	2004-09-06 18:06:51.000000000 -0400
+++ shadow/65406.tmp.30662	2004-09-07 11:01:35.000000000 -0400
@@ -1,14 +1,14 @@
 Bug#: 65406
 Product: Mono: Runtime
 Version: unspecified
+OS: unknown
 OS Details: 
-Status: NEW   
+Status: RESOLVED   
+Resolution: NOTABUG
+Severity: Unknown
 Priority: Major
 Component: misc
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: bmaurer@users.sf.net               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
@@ -42,6 +42,17 @@
 Once all the threads are done executing, the memory usage should get very
 small. However, the memory usage stays constant at about 100 MB, meaning
 none of the arrays was feed.
+------- Additional Comments From lupus@ximian.com  2004-09-07 11:01 -------
+The current default GC build won't release the heap memory back to the
+system, so the comment about memory not shrinking is meaningless.
+If you get rid of the sleep calls and put the QueueUserWorkItem loop
+inside the while(true) loop, you'll actually test if the threadpool
+leaks and you'll see that the amount of memory is basically constant
+(35-40 VSZ, 8 MB RSS for me). The RSS just changes by 30KB after 10
+minutes and this is a small change that could depend on many factors
+(VSZ didn't change): feel free to run the test for a few hours and
+reopen if you have any actual data.