[Mono-bugs] [Bug 53177][Nor] Changed - WaitHandles are not finalizing
Thu, 22 Jan 2004 10:15:37 -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 email@example.com.
--- shadow/53177 2004-01-22 03:57:40.000000000 -0500
+++ shadow/53177.tmp.15468 2004-01-22 10:15:37.000000000 -0500
@@ -186,6 +186,39 @@
------- Additional Comments From firstname.lastname@example.org 2004-01-22 03:57 -------
Created an attachment (id=6498)
+------- Additional Comments From email@example.com 2004-01-22 10:15 -------
+You GC runs right, mine does not. Is it straight GC6.2 or did you
+make changes? What OS?
+Windows appears to get into a race/starvation/etc problem early on
+(first guess is mono_manage_threads() call) while the whole world
+blocks for a join) At about this time, GC goes crazy (excerpt from
+Increasing heap size by 1044480 after 44052 allocated bytes
+Increasing heap size by 1392640 after 44052 allocated bytes
+Initiating full world-stop collection 2 after 1045064 allocd bytes
+--> Marking for collection 2 after 1045064 allocd bytes + 5528 wasted
+Collection 1 finished ---> heapsize = 2568192 bytes
+World-stopped marking took 20 msecs
+Complete collection took 20 msecs
+Increasing heap size by 1859584 after 0 allocated bytes
+Increasing heap size by 2478080 after 0 allocated bytes
+Increasing heap size by 3305472 after 0 allocated bytes
+Increasing heap size by 4407296 after 0 allocated bytes
+Increasing heap size by 5873664 after 0 allocated bytes
+Increasing heap size by 7831552 after 2002152 allocated bytes
+Nothing is malloc'ing memory, but GC is using the algorithm to grow
+the heap exponentially.
+Also, Windows appears to grow heap on nearly every alloc,
+but on your OS it works as it should.
+Keep this open while I set up a few test scenarios. We
+are gonna solve this thing and put it to bed.....