[Mono-bugs] [Bug 53177][Nor] Changed - WaitHandles are not finalizing

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Thu, 22 Jan 2004 00:04:43 -0500 (EST)


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

--- shadow/53177	2004-01-21 13:32:12.000000000 -0500
+++ shadow/53177.tmp.11353	2004-01-22 00:04:43.000000000 -0500
@@ -1,14 +1,14 @@
 Bug#: 53177
 Product: Mono/Runtime
 Version: unspecified
-OS: 
+OS: unknown
 OS Details: 
-Status: NEW   
-Resolution: 
-Severity: 
+Status: RESOLVED   
+Resolution: WONTFIX
+Severity: Unknown
 Priority: Normal
 Component: misc
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: derek.mcumber@datamtnsol.com               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
@@ -110,6 +110,32 @@
 Additional Information:
 
 ------- Additional Comments From derek.mcumber@datamtnsol.com  2004-01-21 13:32 -------
 Created an attachment (id=6491)
 simple test case that uses WaitCallbacks
 
+
+------- Additional Comments From gonzalo@ximian.com  2004-01-22 00:04 -------
+After hitting ENTER i get this:
+
+-----
+Finished Processing
+ 
+Finalize run on 0x80f2f50 System.Threading.Thread
+Finalize run on 0x81fbdc0 System.Globalization.CompareInfo
+Finalize run on 0x80f2870 System.Threading.Thread
+Finalize run on 0x81fd9f0 System.Threading.WaitHandle
+Finalize run on 0x80f2af0 System.IO.FileStream
+Finalize run on 0x81fddb0 System.Threading.AutoResetEvent
+Finalize run on 0x81fbdf0 System.Globalization.CompareInfo
+Finalize run on 0x80f2b40 System.IO.FileStream
+Finalize run on 0x80eecb0 System.IO.StreamWriter
+Finalize run on 0x80eed20 System.IO.StreamWriter
+Finalize run on 0x80f2b90 System.IO.FileStream
+Finalize run on 0x80eed58 System.IO.StreamWriter
+-----
+
+That's the usual stuff (Console.In, Out...) plus a couple of Threads.
+The list varies slightly from run to run.
+
+May be in your case (is that windows?) the GC still sees the pointers
+and doesn't finalize those objects...