[Gc] GC_malloc bug?
mental at rydia.net
Fri Dec 3 23:25:15 PST 2004
On Mon, 2004-11-29 at 14:40, Boehm, Hans wrote:
> It would be interesting to know whether you are trying to allocate
> a particularly large object at the time. GC_PRINT_STATS output
> while it's in this loop might also be enlightening.
The attempted allocation is 415 bytes in size. Any tips for getting the
dynamic linker to resolve a symbol for gdb? Currently GC_print_stats
isn't getting resolved so I can't call it from gdb.
> > -----Original Message-----
> > From: gc-bounces at napali.hpl.hp.com
> > [mailto:gc-bounces at napali.hpl.hp.com]On Behalf Of MenTaLguY
> > Sent: Sunday, November 28, 2004 10:34 PM
> > To: gc at napali.hpl.hp.com
> > Subject: [Gc] GC_malloc bug?
> > With Inkscape, we've been having trouble with hangs resulting from
> > GC_malloc() going into apparently infinite loops, calling
> > GC_collect_or_expand() repeatedly. It seems to be more common on
> > Windows than Linux, but happens on both platforms.
> > The heap isn't normally particularly large at the time (maybe
> > 15MB), and
> > in our case we also have GC_no_dls turned on, so there really
> > shouldn't
> > be that much to trace.
> > The one slightly unusual thing we do is that we currently allocate a
> > very large number of small objects with GC_malloc_uncollectable(); I
> > don't know whether that is likely to create a pathological
> > case for the
> > collector.
> > We're using libgc 6.3; can anyone give me advice for further
> > diagnosing
> > the problem?
> > -mental
> Gc mailing list
> Gc at linux.hpl.hp.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: This is a digitally signed message part
Url : https://napali.hpl.hp.com/pipermail/gc/attachments/20041204/fd2f40ff/attachment.pgp
More information about the Gc