Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: xclerc <xavier.clerc@inria.fr>
To: Caml List <caml-list@inria.fr>
Cc: xclerc Clerc <xavier.clerc@inria.fr>
Subject: Re: [Caml-list] Structural avoidance of memory leaks?
Date: Wed, 9 Feb 2011 10:28:56 +0100	[thread overview]
Message-ID: <D497408E-A77E-4A71-8719-9FACBA335413@inria.fr> (raw)
In-Reply-To: <AANLkTimUP9rMZbmf+XCiLZqqrYrW26vKPFEeJRQ7_JAn@mail.gmail.com>


Le 9 févr. 2011 à 09:47, David MENTRE a écrit :

> Hello Mr. Garrigue,
> 
> 2011/2/9 Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>:
>> * Memory leaks: have to be careful that you are not referencing dead data, preventing the GC from freeing it.
> 
> I thought for a long time that having a GC would avoid any memory
> leak. It appears that this is not the case. Java programmers are well
> aware of the issue and apparently Haskell and OCaml programmers also.

The Java literature about this problem is in fact quite abundant.
One reason for this being that Java is widely used for server-side
applications that have a very long lifetime (think webserver, and
the like). This is why J2EE developer are particularly aware of the
problem. I would add that a related problem to some leaks in these
systems is security (e. g. keeping passwords or other sensitive information
in memory longer than needed).This is probably a problem some
OCaml developer face, maybe Ocsigen developers and/or users.

Finally, if you read some Java papers that refers to the "jconsole"
tool to discover such leaks, the closest OCaml equivalent I can
think of is ocamlviz:
	http://ocamlviz.forge.ocamlcore.org/


Hope this helps,

Xavier Clerc



  reply	other threads:[~2011-02-09  9:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-09  8:47 David MENTRE
2011-02-09  9:28 ` xclerc [this message]
2011-02-09 23:50 ` Raoul Duke
2011-02-10 14:04   ` David Baelde

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=D497408E-A77E-4A71-8719-9FACBA335413@inria.fr \
    --to=xavier.clerc@inria.fr \
    --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