[Mono-bugs] [Bug 74612][Nor] Changed - Unref messages

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Fri, 15 Apr 2005 03:29:30 -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 michi@zeroc.com.


--- shadow/74612	2005-04-15 03:05:55.000000000 -0400
+++ shadow/74612.tmp.12092	2005-04-15 03:29:30.000000000 -0400
@@ -38,6 +38,17 @@
 About once every 30 runs.
 ------- Additional Comments From michi@zeroc.com  2005-04-15 03:05 -------
 Additional info: this happens when my process calls
 System.Environment.Exit(), so the problem happens as the process is
 being dismantled.
+------- Additional Comments From michi@zeroc.com  2005-04-15 03:29 -------
+Yet more info: it looks like problem is caused by a call to
+System.Console.WriteLine() from within an object's destructor. It
+looks like the GC calls the destructor while the program is somewhere
+in the guts of System.Environment.Exit(). The destructor of the object
+tries to write to the console but, I suspect, by then the I/O
+subsystem has been dismantled, and something goes wrong at that point.
+So, question: is it legal for an object's destructor to write to the
+console if that destructor runs as a result of calling Exit()?