unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Han-Wen Nienhuys <hanwen@xs4all.nl>
Cc: guile-devel@gnu.org, Marius Vollmer <mvo@zagadka.de>
Subject: Re: module GC bug
Date: Fri, 05 Aug 2005 16:48:00 +0200	[thread overview]
Message-ID: <42F37C20.7040709@xs4all.nl> (raw)
In-Reply-To: <42F1DF3E.70204@xs4all.nl>

Han-Wen Nienhuys wrote:
> I'm not convinced that you have fixed the original problem. I've CVS 
> upped GUILE, and now LilyPond is again soaring to 750mb memory 
> footprints while processing many trivial files. The problem is a little 
> more acute, since I've upped the GC yield for performance reasons.
> 
> And... this version of Lily even has the kludge I built for 1.6: ie. 
> clearing the 'module property, and replacing scm_stand_in_procs with a 
> weak key hash table.

Paint my face in fluorescent blushing red. This leak was actually caused 
by   me forgetting to #define MODULE_GC_KLUDGE. Case closed, I hope!


-- 
  Han-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


      parent reply	other threads:[~2005-08-05 14:48 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-09 23:32 module GC bug Han-Wen Nienhuys
2005-06-10  6:32 ` Neil Jerram
2005-06-10 11:48   ` Han-Wen Nienhuys
2005-06-19 13:32   ` Han-Wen Nienhuys
2005-06-19 17:33     ` Rob Browning
2005-07-07 18:48     ` Marius Vollmer
2005-06-24 17:50   ` Han-Wen Nienhuys
2005-07-07 18:42 ` Marius Vollmer
2005-07-08  9:24   ` Mikael Djurfeldt
2005-07-09  8:28     ` Han-Wen Nienhuys
2005-07-09 19:28       ` Mikael Djurfeldt
2005-07-09 23:25         ` Han-Wen Nienhuys
2005-07-10  8:16           ` Mikael Djurfeldt
2005-07-09 23:32         ` Han-Wen Nienhuys
2005-07-10  8:17           ` Mikael Djurfeldt
2005-07-08 21:43   ` Han-Wen Nienhuys
2005-07-13 21:02     ` Marius Vollmer
2005-07-13 22:19       ` Han-Wen Nienhuys
2005-07-16 18:57         ` Marius Vollmer
2005-07-17 18:50           ` Han-Wen Nienhuys
2005-07-17 20:44             ` Marius Vollmer
2005-07-18 13:43               ` Han-Wen Nienhuys
2005-08-01  0:20 ` Marius Vollmer
2005-08-01 11:04   ` Han-Wen Nienhuys
2005-08-10 22:29     ` Marius Vollmer
2005-08-15 23:57       ` Rob Browning
2005-08-16  0:10         ` Marius Vollmer
2005-08-16  0:16         ` Rob Browning
2005-08-28 23:31           ` Han-Wen Nienhuys
     [not found]   ` <42EE63F9.4080102@xs4all.nl>
2005-08-02 19:14     ` Marius Vollmer
     [not found]   ` <42F1DF3E.70204@xs4all.nl>
2005-08-05 14:48     ` Han-Wen Nienhuys [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

  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=42F37C20.7040709@xs4all.nl \
    --to=hanwen@xs4all.nl \
    --cc=guile-devel@gnu.org \
    --cc=mvo@zagadka.de \
    /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).