[mercury-users] Debugging 'memory leaks' (fwd)

Peter Wang novalazy at gmail.com
Mon Mar 31 12:04:29 AEDT 2008

On 2008-03-28, Ondrej Bojar <bojar at ufal.ms.mff.cuni.cz> wrote:
> Thanks for GC_PRINT_STATS. The output indicates that during computation 
> (and allocation of some structures), every once a while, gc increases the 
> heap size:
> ...
> Increasing heap size by 16777216 after 391396864 allocated bytes
> Increasing heap size by 16777216 after 409847296 allocated bytes
> ...
> Other lines talk about garbage collection and reclaimed space. Garbage 
> collection happens spontaneously sometimes, and always when I call 
> gc.garbage_collect. Nearly always, some or a lot of space is reclaimed, but 
> the heapsize never sinks, as show in the truncated log below.

That's the normal behaviour without munmap, so unless the heap seems to
keep growing without bound, I wouldn't worry about it.

> I will try using --boehm-gc-munmap as soon as I get a recent ROTD compiled.
> Thanks!
>   Ondrej.


mercury-users mailing list
Post messages to:       mercury-users at csse.unimelb.edu.au
Administrative Queries: owner-mercury-users at csse.unimelb.edu.au
Subscriptions:          mercury-users-request at csse.unimelb.edu.au

More information about the users mailing list