From: Satoshi Ogasawara <ogasawara@itpl.co.jp>
To: caml-list@yquem.inria.fr
Subject: Re: Event.channel memory leak?
Date: Tue, 2 Mar 2010 13:40:24 +0900 [thread overview]
Message-ID: <206B7535-3701-4314-AFAB-F07AD76C045C@itpl.co.jp> (raw)
In-Reply-To: <20100301223402.86592074.ygrekheretix@gmail.com>
On 2010/03/02, at 5:34, ygrek wrote:
> On Mon, 1 Mar 2010 17:04:31 +0900
> Satoshi Ogasawara <ogasawara@itpl.co.jp> wrote:
>> But, the next code makes increasing of memory use rapidly in my environment.
>> (version 3.11.2 on MacOS X leopard)
> Using Gc.compact instead of Gc.full_major doesn't exhibit such behaviour.
Gc.compact works fine. Thank you for usefull comment. I did't understand the meanings
of Gc.full_major.
So, I'll release concurrent cell( http://forge.ocamlcore.org/projects/ccell/ ) version 3.0
include FRP features after checking a few more memory behavior.
---
ogasawara satoshi
prev parent reply other threads:[~2010-03-02 4:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-01 8:04 Satoshi Ogasawara
2010-03-01 20:34 ` [Caml-list] " ygrek
2010-03-02 4:40 ` Satoshi Ogasawara [this message]
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=206B7535-3701-4314-AFAB-F07AD76C045C@itpl.co.jp \
--to=ogasawara@itpl.co.jp \
--cc=caml-list@yquem.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).