This is the mail archive of the guile@sourceware.cygnus.com mailing list for the Guile project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: Guile GC behaviour


Christian Lynbech <chl@tbit.dk> writes:

> Would it be any help to investigate the problem with heap expansion
> turned off?
> 
> The idea would be to set the initial heap segment size to something
> usefully large and then to prevent guile/scwm from allocating more
> heap segments. This would probably lead to more gc'ing but the size
> contribution from the heap would be known and fixed.

What will happen if GCing is turned off (and heap expansion is disabled)
and the heap runs out of space?

> Even though guile calls malloc for other things than heap segments
> (for instance in scm_makstr) this would at least be able to
> demonstrate whether or not the growth in process size is (primarily)
> due to heap expansion or "genuine" memory leaks elsewhere.
> 
> The function to investigate could be 'alloc_some_heap'.

Perhaps-- thanks for pointing this possibility out-- these are exactly
the kinds of suggestions that I need to start thinking more
intelligently about my options.  Thanks!

Greg

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]