[Mono-bugs] [Bug 75518][Maj] Changed - GC enters infinite loop on some allocation patterns

[bugzilla-daemon at bugzilla.ximian.com]

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 at ximian.com.

http://bugzilla.ximian.com/show_bug.cgi?id=75518

--- shadow/75518	2005-07-13 12:56:09.000000000 -0400
+++ shadow/75518.tmp.3757	2005-07-14 11:12:37.000000000 -0400
@@ -11,13 +11,13 @@
 AssignedTo: lupus at ximian.com                            
 ReportedBy: trow at ximian.com               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
 URL: 
 Cc: 
-Summary: runtime locks up on a simple, non-threaded program
+Summary: GC enters infinite loop on some allocation patterns
 
 I've run into an annoying deadlock while hacking on my heap profiler.  The
 deadlock is in program that reads and analyzes the file containing the GC
 history.  It is a simple, single-threaded program than just opens the
 history file and parses it using a BinaryReader.
 
@@ -100,6 +100,14 @@
 
 ------- Additional Comments From trow at ximian.com  2005-07-11 13:50 -------
 Yes, this is on x86.
 
 ------- Additional Comments From miguel at ximian.com  2005-07-13 12:56 -------
 Paolo, can you try to reproduce this?
+
+------- Additional Comments From lupus at ximian.com  2005-07-14 11:12 -------
+This is not a lock up: the GC enters a state where it needs
+more memory, it runs a GC that fails to clenup enough room, but it
+doesn't expand the heap.
+As a temporary workaround you can set the env var
+GC_INITIAL_HEAP_SIZE=4000000.
+I'm investigating further.