Re: [Caml-list] Str memory leak in 3.06?

[Chris Hecker <checker@d6.com>]

>No, there is no need for explicit deallocation of regexps.  Actually,
>there is no leak either: if you put a call to Gc.major() in the loop,
>memory usage remains constant.

Ah, I thought a Gc.compact () did a major collection (the docs say it 
does), and that didn't help.  Maybe I didn't wait long enough?  I just put 
the Gc.major () in there and waited a long time and it seemed to settle out 
eventually, but only after it had allocated 800MB and had paged the rest of 
the world out, which seems big.  Shouldn't the major collection find that 
there is only one live regexp and collect all of the others, and keep the 
heap way smaller than 800MB?

>What happens is that the speed of the (incremental) major collector
>isn't appropriately adjusted, so it runs too slowly and lets "floating
>garbage" accumulate.  This is a common problem with Caml objects that
>are just handle on resources allocated outside the Caml heap: precise
>determination of the space consumption of the latter is generally
>impossible, causing the incremental major GC to run often too slowly,
>sometimes too fast...

Ah, is there something Str could do to avoid this, like setting the 
mysterious alloc_custom parms differently?  Also, how could I have figured 
this out myself and not bothered the list?

Thanks,
Chris


-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners