From: Liliana Marie Prikler <liliana.prikler@gmail.com>
To: Calvin Heim <frofroggy@gmail.com>, 51366@debbugs.gnu.org
Subject: bug#51366: Pure storage overflow warning in *GNU Emacs* buffer when emacs@27.2 is invoked
Date: Sun, 24 Oct 2021 18:29:28 +0200 [thread overview]
Message-ID: <844cefa2585a788b9c8c342efb56ab8a5c7dcf05.camel@gmail.com> (raw)
In-Reply-To: <5211057826cc8dfa6d3e76b0f6effa1333202972.camel@gmail.com>
Small followup:
Am Samstag, den 23.10.2021, 20:31 -0700 schrieb Calvin Heim:
> > Warning Warning!!! Pure space overflow !!!Warning Warning
> > (See the node Pure Storage in the Lisp manual for details.)
Said node says
> If Emacs will be dumped using the ‘pdump’ method (*note Building
> Emacs::), the pure-space overflow is of no special importance (it
> just means some of the preloaded stuff cannot be shared with other
> Emacs jobs). However, if Emacs will be dumped using the now obsolete
> ‘unexec’ method, the resulting image will work, but garbage
> collection (*note Garbage Collection::) is disabled in this
> situation, causing a memory leak.
Guix-built Emacs uses pdumps since 27.1, so garbage collection should
still be enabled. It might also be worth checking the Guix System vs.
foreign distro angle, as
> Such an overflow normally won’t happen unless you try to preload
> additional libraries or add features to the standard ones.
Is there anything noteworthy going on in stuff like LD_PRELOAD?
Regards,
Liliana
next prev parent reply other threads:[~2021-10-24 16:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-24 3:31 bug#51366: Pure storage overflow warning in *GNU Emacs* buffer when emacs@27.2 is invoked Calvin Heim
2021-10-24 16:20 ` Liliana Marie Prikler
2021-10-24 16:29 ` Liliana Marie Prikler [this message]
2021-10-24 18:42 ` Calvin Heim
2021-10-25 21:57 ` Calvin Heim
2022-06-26 10:25 ` Liliana Marie Prikler
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=844cefa2585a788b9c8c342efb56ab8a5c7dcf05.camel@gmail.com \
--to=liliana.prikler@gmail.com \
--cc=51366@debbugs.gnu.org \
--cc=frofroggy@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 public inbox
https://git.savannah.gnu.org/cgit/guix.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).