[Gc] GC_malloc bug?
hans.boehm at hp.com
Tue Dec 7 13:06:06 PST 2004
If you mail it to me, I'll summarize my conclusions. It might be
best to just send the last MB or so.
The larger GC_free_space_divisor explains why it would collect
repeatedly given the large GC_words_wasted values. But I still don't
understand where those are coming from. There may be a long-standing
bug/misfeature here that didn't show up because few people adjust
> -----Original Message-----
> From: gc-bounces at napali.hpl.hp.com
> [mailto:gc-bounces at napali.hpl.hp.com]On Behalf Of Kees Cook
> Sent: Tuesday, December 07, 2004 12:53 PM
> To: gc at napali.hpl.hp.com
> Subject: Re: [Gc] GC_malloc bug?
> On Tue, Dec 07, 2004 at 12:24:11PM -0800, Boehm, Hans wrote:
> > As always, a small test case would be great.
> Alternatively, it would be
> I tried trimming down the document size in Inkscape, but nearly any
> change I made would "fix" the problem. I haven't been able to
> intentionally create this bug, so I've stuck with the one
> document that
> I have where the saved state produces the bug. :)
> > useful to also define GC_DUMP_REGULARLY (the environment
> variable). This
> > will generate much more voluminous output, which might be
> That output is giant. Do you want me to mail it to the list like the
> last one?
> > Are you using a larger GC_free_space_divisor? A
> non-default GC_max_retries?
> A quick grep shows me:
> Didn't find any code for max_tries.
> Kees Cook @outflux.net
> Gc mailing list
> Gc at linux.hpl.hp.com
More information about the Gc