unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Chris Vine <chris@cvine.freeserve.co.uk>
To: Mark H Weaver <mhw@netris.org>
Cc: 19235@debbugs.gnu.org
Subject: bug#19235: make-fresh-user-module procedure leaks memory
Date: Fri, 26 Dec 2014 18:26:08 +0000	[thread overview]
Message-ID: <20141226182608.24c7dabf@bother.homenet> (raw)
In-Reply-To: <20141207141903.1347c764@bother.homenet>

As far as I can tell the make-fresh-user-module procedure is not called
by guile itself, and providing a global mutex for it with a binding
enabling it to be called from scheme code seems to work fine.

This also makes it straightforward to incorporate in a thread-safe
way the code you suggested to free stale user modules.  However, as I
mentioned, I am a bit reluctant to incorporate code which might break
in the future.  Is there any possibility that a "delete-module!"
procedure could be included within the public guile API for the next
release of guile?  It seems like something that could be useful to
anyone using non-default user modules in their code.

Chris





  reply	other threads:[~2014-12-26 18:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-30 23:28 bug#19235: make-fresh-user-module procedure leaks memory Chris Vine
2014-12-07  8:07 ` Mark H Weaver
2014-12-07 14:19   ` Chris Vine
2014-12-26 18:26     ` Chris Vine [this message]
2016-06-22 17:52       ` Andy Wingo
2016-06-23 14:17         ` Mark H Weaver
2016-06-24  8:04           ` bug#15602: " Ludovic Courtès
2016-06-26  0:50             ` Mark H Weaver

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141226182608.24c7dabf@bother.homenet \
    --to=chris@cvine.freeserve.co.uk \
    --cc=19235@debbugs.gnu.org \
    --cc=mhw@netris.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 read-only IMAP folder(s) and NNTP newsgroup(s).