all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: Tom Gillespie <tgbugs@gmail.com>,
	56623@debbugs.gnu.org, greghendershott@gmail.com
Subject: bug#56623: memory leak introduced by new nonrecursive lisp reader
Date: Mon, 29 Aug 2022 11:38:06 +0200	[thread overview]
Message-ID: <m2fshf2xvl.fsf@Mini.fritz.box> (raw)
In-Reply-To: <m21qszjv5t.fsf@Mini.fritz.box> ("Gerd Möllmann"'s message of "Mon, 29 Aug 2022 10:44:46 +0200")

Gerd Möllmann <gerd.moellmann@gmail.com> writes:

> Mattias Engdegård <mattiase@acm.org> writes:
>
>> If either makes things better, maybe we can come up with a solution
>> that doesn't hurt performance.
>
> This might be completely off, but anyway:
>
> lread.c uses free_cons.  Is it certain that the cons cell is never
> marked at that point?  Not that I see it happening, or could explain how
> exactly GC would run while that code executes.  Maybe it's worth adding
> a check in free_cons?

One candidate: A hash table with user-defined :test.  Invoking the
user-defined functions can GC.





      reply	other threads:[~2022-08-29  9:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-17 22:03 bug#56623: memory leak introduced by new nonrecursive lisp reader Tom Gillespie
2022-07-18 11:21 ` Mattias Engdegård
2022-07-27  9:20   ` Mattias Engdegård
2022-08-27 15:35     ` Lars Ingebrigtsen
2022-08-28 17:29       ` Greg Hendershott
2022-08-28 21:06         ` Tom Gillespie
2022-08-29 12:59           ` Greg Hendershott
2022-08-29 15:20             ` Mattias Engdegård
2022-08-29 15:52               ` Mattias Engdegård
2022-08-29  8:44     ` Gerd Möllmann
2022-08-29  9:38       ` Gerd Möllmann [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

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

  git send-email \
    --in-reply-to=m2fshf2xvl.fsf@Mini.fritz.box \
    --to=gerd.moellmann@gmail.com \
    --cc=56623@debbugs.gnu.org \
    --cc=greghendershott@gmail.com \
    --cc=mattiase@acm.org \
    --cc=tgbugs@gmail.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.
Code repositories for project(s) associated with this external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.