caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: David MENTRE <dmentre@linux-france.org>
To: Jacques Garrigue <garrigue@math.nagoya-u.ac.jp>
Cc: orbitz@ezabel.com, caml-list@inria.fr
Subject: [Caml-list] Structural avoidance of memory leaks?
Date: Wed, 9 Feb 2011 09:47:18 +0100	[thread overview]
Message-ID: <AANLkTimUP9rMZbmf+XCiLZqqrYrW26vKPFEeJRQ7_JAn@mail.gmail.com> (raw)

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.

Is there a documentation/paper/blog post/other somewhere that:
  * Explains where those memory leaks are coming from (i.e. more
precisely that "not referencing dead data")? Is there a taxonomy? Are
they tied to a specific language or are they generic to any language?
For example, in OCaml are memory leaks linked to imperative aspects or
can I have memory leaks using only purely functional aspects of the
language?

 * Tells me, as a practitioner, how to *structurally* avoid those
memory leaks? For example by avoiding some data structures or certain
kind of expressions.

Sincerely yours,
david

             reply	other threads:[~2011-02-09  8:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-09  8:47 David MENTRE [this message]
2011-02-09  9:28 ` xclerc
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=AANLkTimUP9rMZbmf+XCiLZqqrYrW26vKPFEeJRQ7_JAn@mail.gmail.com \
    --to=dmentre@linux-france.org \
    --cc=caml-list@inria.fr \
    --cc=garrigue@math.nagoya-u.ac.jp \
    --cc=orbitz@ezabel.com \
    /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).