unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Anand Mohanadoss <anand108@gmail.com>
Cc: 19180-done@debbugs.gnu.org, "Ludovic Courtès" <ludo@gnu.org>,
	"Linas Vepstas" <linasvepstas@gmail.com>
Subject: bug#19180: guile bug#19180: vacuum_weak_hash_table error
Date: Tue, 12 Jul 2016 09:32:16 +0200	[thread overview]
Message-ID: <877fcr2txb.fsf@pobox.com> (raw)
In-Reply-To: <87twgls26t.fsf@pobox.com> (Andy Wingo's message of "Wed, 22 Jun 2016 16:55:38 +0200")

Hi,

On Wed 22 Jun 2016 16:55, Andy Wingo <wingo@pobox.com> writes:

> On Mon 15 Dec 2014 07:36, Anand Mohanadoss <anand108@gmail.com> writes:
>
>> Vacuum weak hash table assert Table=0x9bdb840 len=0 removed=1
>> orig_len=2321 n_items=2321
>
> I guess printing a warning is not worse than crashing.  I was unable to
> make this table work in a reliable way in 2.0 without rewriting it, so
> in 2.2 there's a new implementation with hopefully no bug in this
> regard.

I changed this assert to a warning and added a comment like this:

          /* The move to BDW-GC with Guile 2.0 introduced some bugs
             related to weak hash tables, threads, memory usage, and the
             alloc lock.  We were unable to fix these issues
             satisfactorily in 2.0 but have addressed them via a rewrite
             in 2.2.  If you see this message often, you probably want
             to upgrade to 2.2.  */

Andy





      parent reply	other threads:[~2016-07-12  7:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAHrUA3554+87CVKsW2OT+-roVeyK4sE+xyDPaGf4ar5fAWQ2+Q@mail.gmail.com>
2014-12-08  7:34 ` bug#19180: guile bug#19180: vacuum_weak_hash_table error Anand Mohanadoss
2014-12-08  9:34   ` Ludovic Courtès
2014-12-15  6:36     ` Anand Mohanadoss
2016-06-22 14:55       ` Andy Wingo
2016-06-22 15:43         ` Anand Mohanadoss
2016-06-22 21:11           ` Linas Vepstas
2016-06-22 21:33           ` Andy Wingo
2016-06-23  4:24             ` Anand Mohanadoss
2016-07-12  7:32         ` Andy Wingo [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=877fcr2txb.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=19180-done@debbugs.gnu.org \
    --cc=anand108@gmail.com \
    --cc=linasvepstas@gmail.com \
    --cc=ludo@gnu.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).