Analysis of Mauve failures - The final chapter

Fri Apr 5 12:16:00 GMT 2002

Boehm, Hans wrote:
> How about the following "solution" for now:
>> 1) We unconditionally suppress all but every Nth instance of this warning.
> (N settable by environment variable replacing GC_NO_BLACKLIST_WARNING,
> defaulting to 3). I expect this eliminates the warning completely for all
> the standard test cases, and 90% of the rest. I'm not too uncomfortable
> with that, since a bounded number of these usually at most indicate a
> bounded space leak.
>> 2) We change the warning message to something like
>> "Repeated allocation of very large block (size %ld): may lead to poor GC
> performance and memory leak."
>> Does this sound reasonable?

That seems ok, though perhaps a higher threshold (10?) might be better.
-- 
	--Per Bothner
per@bothner.com http://www.bothner.com/per/