[Mono-bugs] [Bug 70701][Cri] Changed - use of finalizers causes memory leaks

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Wed, 22 Dec 2004 12:52:17 -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 lupus@ximian.com.


--- shadow/70701	2004-12-20 16:59:11.000000000 -0500
+++ shadow/70701.tmp.32401	2004-12-22 12:52:17.000000000 -0500
@@ -96,6 +96,12 @@
 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.
+------- Additional Comments From lupus@ximian.com  2004-12-22 12:52 -------
+This happens also with an equivalent C program, I sent a report to the
+libgc mailing list.
+Adding a GC.Collect() call stops the leak for me, though, both in mono
+1.0.5 and 1.1.3.