On 10/18/2012 3:37 PM, Christian Thalinger wrote:
Just curious - the test runs with a max of 10 GCs. You
reproduced this bug on a slower machine with fastdebug build.
If you increase the max number of GCs, I wonder how long
the test will take to complete/pass?
Around 14 GCs (runtime with -Xcomp approximately 40 seconds on that particular
machine).
Would increasing the max to 20 fix this bug? I don't have
a strong objection to call System.runFinalization. As I don't
know what behavior the test wants to cover, adjusting the
number of max GC invocations seems a good alternative.
Mandy
