unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@gmail.com>
To: Boruch Baum <boruch_baum@gmx.com>
Cc: 31091@debbugs.gnu.org
Subject: bug#31091: 25.2: Feature Request: auto exit upon memory exhaustion warning
Date: Sun, 08 Apr 2018 13:26:08 -0400	[thread overview]
Message-ID: <87bmetmwy7.fsf@gmail.com> (raw)
In-Reply-To: <20180408165819.bsf534bjiwfsgmx4@E15-2016.optimum.net> (Boruch Baum's message of "Sun, 8 Apr 2018 12:58:19 -0400")

Boruch Baum <boruch_baum@gmx.com> writes:

> On 2018-04-08 12:30, Noam Postavsky wrote:
>> Hmm, I guess I'm not sure what advantage an abrubt shutdown has over a
>> warning.
>
> The most useful case would be of a user is running a time-consuming
> operation or an asynchronous operation, maybe a long repetitive macro,
> for which the current warning would be generated at near the beginning
> of the operation and system freeze would happen in mid-operation.

The final out-of-memory message comes via `signal', so any operation
would be interrupted.  Although the almost-out-of-memory warnings just
use display-warnings, so they don't interrupt anything.

>>  And as far as I understand, you never saw the warnings
>> messages,
>
> I did see the mini-buffer advice and warning, and ignored it, and I did
> see the mode line warning, and ignored it. Added to the long list of
> things I've done -- once.

Hmm, I'm surprised you actually hit the warning.  Are you on a 32 bit
system with about 4GB RAM?  I guess you could hit the 75% warning at 3GB
allocation, and then start swapping soon after, if other processes are
using about 1GB RAM.






  reply	other threads:[~2018-04-08 17:26 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-08  7:22 bug#31091: 25.2: Feature Request: auto exit upon memory exhaustion warning Boruch Baum
2018-04-08  7:51 ` Andreas Schwab
2018-04-08  7:59   ` Boruch Baum
2018-04-08  8:36     ` Andreas Schwab
2018-04-08  8:46       ` Boruch Baum
2018-04-08 11:24         ` Andreas Schwab
2018-04-08 11:49           ` Boruch Baum
2018-04-08 16:10             ` Andreas Schwab
2018-04-08 16:17               ` Boruch Baum
2018-04-08 17:28                 ` Andreas Schwab
2022-04-24 14:25   ` Lars Ingebrigtsen
2018-04-08 12:58 ` Eli Zaretskii
2018-04-08 13:21   ` Boruch Baum
2018-04-08 13:57     ` Eli Zaretskii
2018-04-08 16:21       ` Andreas Schwab
2018-04-08 16:31         ` Noam Postavsky
2018-04-08 16:37         ` Eli Zaretskii
2018-04-08 13:25 ` Noam Postavsky
2018-04-08 13:53   ` Boruch Baum
2018-04-08 15:27 ` Noam Postavsky
2018-04-08 15:54   ` Boruch Baum
2018-04-08 16:13     ` Andreas Schwab
2018-04-08 16:30     ` Noam Postavsky
2018-04-08 16:58       ` Boruch Baum
2018-04-08 17:26         ` Noam Postavsky [this message]
     [not found]           ` <20180408181013.6hw7ec3fi2dvfeja@E15-2016.optimum.net>
2018-04-08 21:58             ` bug#31091: [OFFLIST] " Noam Postavsky

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=87bmetmwy7.fsf@gmail.com \
    --to=npostavs@gmail.com \
    --cc=31091@debbugs.gnu.org \
    --cc=boruch_baum@gmx.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/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).