From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: 46916@debbugs.gnu.org, pipcet@gmail.com
Subject: bug#46916: 28.0.50; pure_alloc(10424, ...) fails badly when pure space is exhausted
Date: Sun, 31 Oct 2021 09:13:57 +0200 [thread overview]
Message-ID: <83h7cxoedm.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkm=_omBoRbF3hkMH4fK4p-ECvLFQigE9-Y1=KoO2mZ2mEQ@mail.gmail.com> (message from Stefan Kangas on Sat, 30 Oct 2021 19:56:42 -0700)
> From: Stefan Kangas <stefan@marxist.se>
> Date: Sat, 30 Oct 2021 19:56:42 -0700
> Cc: Pip Cet <pipcet@gmail.com>, 46916@debbugs.gnu.org
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: Pip Cet <pipcet@gmail.com>
> >> Date: Thu, 4 Mar 2021 12:44:49 +0000
> >>
> >> On Thu, Mar 4, 2021 at 12:26 PM Pip Cet <pipcet@gmail.com> wrote:
> >> > Pure space should be removed. But until it is, it shouldn't exhaust
> >> > all virtual memory, crashing the machines of the unwary ones who tried
> >> > to build emacs without a ulimit...
> >>
> >> This minimal patch "fixes" the issue here, by throwing a fatal error
> >> in this unusual and avoidable situation. No new test as not testable.
> >
> > Just enlarge the pure space amount, and be done with it. That's what
> > we always do when this happens.
>
> There's a patch here that was never installed. Eli didn't sound to
> enthusiastic. Is there anything more left to do here, or should this
> just be closed? Or should purespace be enlarged?
We could enlarge the pure space size, yes. but since no one has yet
reported any problems with that, I tend to do nothing for now.
next prev parent reply other threads:[~2021-10-31 7:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-04 12:24 bug#46916: 28.0.50; pure_alloc(10424, ...) fails badly when pure space is exhausted Pip Cet
2021-03-04 12:44 ` Pip Cet
2021-03-04 14:15 ` Eli Zaretskii
2021-10-31 2:56 ` Stefan Kangas
2021-10-31 7:13 ` Eli Zaretskii [this message]
2021-10-31 9:41 ` Pip Cet
2021-10-31 11:29 ` Eli Zaretskii
2021-10-31 14:02 ` Stefan Kangas
2021-10-31 14:23 ` Eli Zaretskii
2021-11-05 7:11 ` Stefan Kangas
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=83h7cxoedm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=46916@debbugs.gnu.org \
--cc=pipcet@gmail.com \
--cc=stefan@marxist.se \
/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).