unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Hendrik Tews <hendrik.tews@kernkonzept.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 42013@debbugs.gnu.org
Subject: bug#42013: 26.3; hash tables are not garbage collected
Date: Wed, 21 Oct 2020 14:47:45 +0200	[thread overview]
Message-ID: <874kmnoidq.fsf@cert.kernkonzept.com> (raw)
In-Reply-To: <87a6wlt98n.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sat, 17 Oct 2020 12:52:40 +0200")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> => ((vec2 -1) (vec1 4))
>
> Uhmn...

It is not really clear what you executed to obtain the negative
number. I am assuming you executed all the let expressions in
your reply in sequence.

To me, the most obvious explanation for the negative number would
be that garbage-collect does not always perform a full garbage
collection, therefore the last garbage-collect by chance finally
performs a full collection and collects one vector that has
survived the other garbage collections...

> So I'm not sure there's anything to fix here, except perhaps noting in
> the doc string that you can't do precision math on the numbers?  Anybody?

To me the observed behavior suggests that the Elisp garbage
collector is more complicated than the simple mark and sweep
described in the manual. Can you really confirm, that this is not
the case? Because otherwise I would expect a documentation update
for garbage-collect and in the Garbage Collection appendix.

Hendrik





  reply	other threads:[~2020-10-21 12:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-22 22:20 bug#42013: 26.3; hash tables are not garbage collected Hendrik Tews
2020-10-17 10:52 ` Lars Ingebrigtsen
2020-10-21 12:47   ` Hendrik Tews [this message]
2020-10-22 11:22     ` Lars Ingebrigtsen
2020-10-22 12:14 ` Andreas Schwab
2020-10-22 15:15   ` Hendrik Tews
2021-09-16 15:13     ` Lars Ingebrigtsen

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/emacs/

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

  git send-email \
    --in-reply-to=874kmnoidq.fsf@cert.kernkonzept.com \
    --to=hendrik.tews@kernkonzept.com \
    --cc=42013@debbugs.gnu.org \
    --cc=larsi@gnus.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).