This is the mail archive of the
java@gcc.gnu.org
mailing list for the Java project.
Re: Analysis of Mauve failures - The final chapter
- From: Per Bothner <per at bothner dot com>
- To: "Boehm, Hans" <hans_boehm at hp dot com>
- Cc: java at gcc dot gnu dot org
- Date: Fri, 05 Apr 2002 11:42:21 -0800
- Subject: Re: Analysis of Mauve failures - The final chapter
- References: <40700B4C02ABD5119F000090278766443BF177@hplex1.hpl.hp.com>
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/