PR 10920 GC reports "too many roots"
Mon Nov 24 21:24:00 GMT 2003
I haven't thought about it enough. I don't think it's trivial, since a lot of
the root sets would need to be added and perhaps allocated during a GC. GC_scratch_alloc might
still work, but there's some danger that you would make it much less likely to
be able to recover from an out-of-memory condition, since it would then tend to
show up as a failure to allocate the root sets during a GC. Perhaps we could
overallocate during startup to make it unlikely that the table would need to
expand later on.
I think there really shouldn't be a problem unless/until we end up with a separate
root set per class. I'll think about better ways to handle that.
> -----Original Message-----
> From: Jeff Sturm [mailto:firstname.lastname@example.org]
> Sent: Monday, November 24, 2003 12:27 PM
> To: Boehm, Hans
> Cc: 'Øyvind Harboe'; email@example.com
> Subject: RE: PR 10920 GC reports "too many roots"
> On Mon, 24 Nov 2003, Boehm, Hans wrote:
> > The table size is MAX_ROOT_SETS. GC_dump() should print
> what's currently
> > in the table. It would be good to understand why it's
> overflowing. But simply
> > increasing MAX_ROOT_SETS is likely to improve matters.
> Hans, is there any good reason this table is not yet sized
More information about the Java