Analysis of Mauve failures - The final chapter

Fri Apr 5 01:15:00 GMT 2002

Boehm, Hans writes:
 > > From: Mark Wielaard [mailto:mark@klomp.org]
 > > > !java.lang.reflect.Array.newInstance
 > > Ugh, not fun. Running by hand also hangs, but turning on the -debug or
 > > -verbose flag makes it run... When not giving any flags it only prints
 > > Needed to allocate blacklisted block at 0x824b000
 > > The test actually tries to force a OutOfMemoryError exception which
 > > might explain this. But the Object.clone() test also seems to do this
 > > and that one just works.
 > All tests that allocate large objects should ideally be run with the
 > environment variable GC_NO_BLACKLIST_WARNING defined. That will get rid of
 > the message. The occurrence of the warning is often less than 100%
 > deterministic, and that's expected. Was there an issue here beyond the
 > warning?
Hans,
I don't understand. If the gc isn't buggy, why does it produce this
warning at all in a production quality system?
Andrew.