From: Philipp Stephani <p.stephani2@gmail.com>
To: Nicolas Petton <nico@petton.fr>
Cc: 42482@debbugs.gnu.org, "Milan Stanojević" <mstanojevic@janestreet.com>
Subject: bug#42482: 27.0.91; emacs modules memory leak
Date: Sat, 1 Aug 2020 16:47:18 +0200 [thread overview]
Message-ID: <CAArVCkR0_Y8YK9G+UejjwpjNBK_O1TWLnKp2xjzAR+D=5A1sjA@mail.gmail.com> (raw)
In-Reply-To: <87zh7er0e2.fsf@petton.fr>
Am Sa., 1. Aug. 2020 um 14:55 Uhr schrieb Nicolas Petton <nico@petton.fr>:
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> I've now added a few more tests and backported the fix to the release branch.
> >
> > I think it's too late for Emacs 27.1, sorry. The tarball is already
> > made.
>
> If the bugfix is important enough, I can build a new RC tomorrow and set
> the release date to the 8th of Aug.
I don't feel strongly either way. My expectation for global references
is that they should mainly be used for the module equivalent of defvar
and friends, in which case the bug isn't that severe because nobody
needs millions of defvars. OTOH, people might use global references
for other means, including allocating them dynamically, in which case
leaking them can become annoying.
next prev parent reply other threads:[~2020-08-01 14:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 23:25 bug#42482: 27.0.91; emacs modules memory leak Milan Stanojević
2020-07-23 12:06 ` Philipp Stephani
2020-07-23 14:29 ` Milan Stanojević
2020-07-23 14:33 ` Philipp Stephani
2020-07-23 17:45 ` Eli Zaretskii
2020-07-23 19:11 ` Milan Stanojević
2020-07-25 21:43 ` Philipp Stephani
2020-08-01 12:11 ` Philipp Stephani
2020-08-01 12:37 ` Eli Zaretskii
2020-08-01 12:55 ` Nicolas Petton
2020-08-01 14:47 ` Philipp Stephani [this message]
2020-08-02 17:25 ` Eli Zaretskii
2020-08-03 23:02 ` Milan Stanojević
2020-08-04 8:05 ` Nicolas Petton
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='CAArVCkR0_Y8YK9G+UejjwpjNBK_O1TWLnKp2xjzAR+D=5A1sjA@mail.gmail.com' \
--to=p.stephani2@gmail.com \
--cc=42482@debbugs.gnu.org \
--cc=mstanojevic@janestreet.com \
--cc=nico@petton.fr \
/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.