From: Kenneth Adam Miller <kennethadammiller@gmail.com>
To: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] Potential OCaml-ZMQ memory management problems
Date: Thu, 4 Dec 2014 03:02:29 -0500 [thread overview]
Message-ID: <CAK7rcp98sHmpn7-e7Sj68YPRjES1J+PZbriOGoUB5kd+2BGhZg@mail.gmail.com> (raw)
In-Reply-To: <54801373.3010506@fugmann.net>
[-- Attachment #1: Type: text/plain, Size: 2065 bytes --]
I'm using zmq and ocaml-zmq as installed by opam; I'm not at my work
computer or I would provide those details.
Yes, I will try to work on creating a reproducible script
Could it possibly be a call to Tunegc.set_gc () from
https://github.com/argp/bap/blob/master/ocaml/tunegc.ml ?
I notice that this error didn't appear in single calls to my utility;
basically, I'm using iltrans from bap and I'm using it in a long living
process, unlike the current implementation which expects a few
transformations and then process death. I did notice that when I run it, if
I'm watching system monitor that it begins consuming vast amounts of memory
(quickly grows from a few megabytes to 800+) before it hits segfault. Would
there be any way to restore the aggressiveness of the GC between calls to
iltrans?
On Thu, Dec 4, 2014 at 2:55 AM, Anders Fugmann <anders@fugmann.net> wrote:
> Hi Kenneth,
>
> The Ocaml-zmq code copies data from received messages into memory under
> the control of the ocaml garbage collector, and immediatly frees the ZMQ
> buffers.
>
> You do not need to explicitly free the data received from call to recv.
>
> Can you produce a small sample code that exposes the problem? We are using
> the ocaml-zmq binding extensively, and have not seen any problems.
>
> If I were to take a wild guess, it either a mismatch between library
> versions or the garbage-collector collecting the socket or zmq context.
>
> What version of the ocaml-zmq bindings and libzmq (c impl) are you using?
>
> /Anders
>
>
>
> On 12/04/2014 07:09 AM, Kenneth Adam Miller wrote:
>
>> I'm using ocaml-zmq (https://github.com/issuu/ocaml-zmq) and I think I'm
>> encountering a memory management issue. I could be wrong however, but
>> basically the issue (I think) is I have a rather large set of messages
>> to send via zmq, and I'm getting a segfault.
>>
>> Does anybody know if I need to free the strings received from zmq recv
>> functions in ocaml? If so how do I do that from ocaml?
>>
>> There's no code because this is just a general novice ocaml questions.
>>
>
>
[-- Attachment #2: Type: text/html, Size: 2905 bytes --]
next prev parent reply other threads:[~2014-12-04 8:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 6:09 Kenneth Adam Miller
2014-12-04 7:55 ` Anders Fugmann
2014-12-04 8:02 ` Kenneth Adam Miller [this message]
2014-12-04 9:59 ` Anders Fugmann
2014-12-04 10:04 ` Kenneth Adam Miller
2014-12-04 16:39 ` Kenneth Adam Miller
2014-12-04 16:45 ` Kenneth Adam Miller
2014-12-04 19:36 ` Anders Peter Fugmann
2014-12-04 21:48 ` Kenneth Adam Miller
2014-12-05 9:14 ` Anders Fugmann
2014-12-05 14:38 ` Kenneth Adam Miller
2014-12-08 18:11 ` Kenneth Adam Miller
2014-12-08 18:16 ` Yotam Barnoy
2014-12-08 18:19 ` Kenneth Adam Miller
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=CAK7rcp98sHmpn7-e7Sj68YPRjES1J+PZbriOGoUB5kd+2BGhZg@mail.gmail.com \
--to=kennethadammiller@gmail.com \
--cc=caml-list@inria.fr \
/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).