From: "Maxime Ransan (BLOOMBERG/ 731 LEX)" <mransan@bloomberg.net>
To: rich@annexia.org
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Finding "lost" references to OCaml heap values
Date: Tue, 6 Oct 2015 13:57:52 -0000 [thread overview]
Message-ID: <5613D36001C106E20039047E_0_58858@p057> (raw)
[-- Attachment #1: Type: text/plain, Size: 1431 bytes --]
Just a hint about why the destructor is not called is that when using caml_alloc_custom at https://github.com/libguestfs/libguestfs/blob/master/v2v/xml-c.c#L139, you are setting the used parameter to 0.
As mentioned in http://caml.inria.fr/pub/docs/manual-ocaml-4.00/manual033.html#toc150 you can increase the ratio. A quick check would be to use a (used = 1, max = 1).
From: rich@annexia.org At: Oct 6 2015 09:43:53
To: caml-list@inria.fr
Subject: Re:[Caml-list] Finding "lost" references to OCaml heap values
I guess I have two questions:
(1) Is calling Gc.compact () guaranteed to call the finalizer of any
object which is no longer reachable, under all circumstances? Or
would there be some case where it wouldn't be called?
(2) I have a large mixed OCaml / C program[a] where somehow calling
Gc.compact isn't calling the destructor of a (very) large object.
Manual code inspection has not revealed anything so far --
superficially it appears we are not holding any references to the
object. Is there any method / library / tool that can inspect the
OCaml heap and find references to an object?
Rich.
[a] https://github.com/libguestfs/libguestfs/tree/master/v2v
--
Richard Jones
Red Hat
--
Caml-list mailing list. Subscription management and archives:
https://sympa.inria.fr/sympa/arc/caml-list
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
Bug reports: http://caml.inria.fr/bin/caml-bugs
[-- Attachment #2: Type: text/html, Size: 3370 bytes --]
next reply other threads:[~2015-10-06 13:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 13:57 Maxime Ransan (BLOOMBERG/ 731 LEX) [this message]
2015-10-06 15:53 ` Richard W.M. Jones
2015-10-06 15:57 ` Richard W.M. Jones
-- strict thread matches above, loose matches on Subject: below --
2015-10-06 13:43 Richard W.M. Jones
2015-10-06 14:16 ` Richard W.M. Jones
2015-10-06 15:09 ` Gerd Stolpmann
2015-10-06 15:17 ` Gabriel Scherer
2015-10-06 15:54 ` Richard W.M. Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5613D36001C106E20039047E_0_58858@p057 \
--to=mransan@bloomberg.net \
--cc=caml-list@inria.fr \
--cc=rich@annexia.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).