Re: [Caml-list] Understanding usage by the runtime

[orbitz@ezabel.com]

Being on the C side is not even something I had considered.  In this case, I think the only piece of code not part of the Ocaml RTS that is talking to C is Lwt.  It is possible that there is a memory leak in there somewhere.  The upside, though, is there seems to be some residue of it in the Ocaml side.  My heap numbers given earlier are ~65megs which is significantly larger than it should be, so I might be able to track it down from the Ocaml side. 

Thank you for the suggestion of ocaml-memprof.

/M

On Dec 31, 2011, at 4:11 AM, David Baelde wrote:

> Hi,
> 
> My thoughts are not so fresh on that topic but, seeing the figures, it
> could very well be that your memory leak is on the C side. Memory
> allocated using malloc in C to Caml bindings won't show up in the Gc
> info.
> 
> By the way, if you're sure that the leak is on the OCaml side, you
> might be interested in ocaml-memprof. It's a patch by Fabrice Le
> Fessant to get precise info about what kind of object is allocated by
> the Gc over time. We've been able to use it a while ago on liquidsoap,
> after Samuel Mimram adapted it for Ocaml 3.10 (you can find the
> updated patch on his page).
> 
> Hope this helps,
> 
> David