[Mono-bugs] [Bug 70701][Cri] Changed - use of finalizers causes memory leaks
bugzilla-daemon@bugzilla.ximian.com
bugzilla-daemon@bugzilla.ximian.com
Mon, 20 Dec 2004 16:59:11 -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 will@cambia.com.
http://bugzilla.ximian.com/show_bug.cgi?id=70701
--- shadow/70701 2004-12-20 15:03:21.000000000 -0500
+++ shadow/70701.tmp.17119 2004-12-20 16:59:11.000000000 -0500
@@ -2,13 +2,13 @@
Product: Mono: Runtime
Version: 1.0
OS: Red Hat 9.0
OS Details: Fedora Core 2
Status: NEW
Resolution:
-Severity:
+Severity: Unknown
Priority: Critical
Component: misc
AssignedTo: mono-bugs@ximian.com
ReportedBy: will@cambia.com
QAContact: mono-bugs@ximian.com
TargetMilestone: ---
@@ -88,6 +88,14 @@
Microsoft .NET continues to run the example indefinitely, as does mono if
line 39 (~Final() {}) is commented out.
How often does this happen?
Every time.
+
+------- Additional Comments From will@cambia.com 2004-12-20 16:59 -------
+Another twist to this bug: when it occurs, logging shows that many
+of the finalizers aren't being called until the program exits and
+the domain unloads. Inserting calls to
+GC.Collect/WaitForPendingFinalizers causes the finalizers to be
+called correctly, however the program still leaks memory, so it is
+unknown as to whether the two bad behaviors are linked.