all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Emacs on Android OOMs with pdf-tools. (And an Android howto.)
Date: Thu, 22 Aug 2024 13:16:55 +0300	[thread overview]
Message-ID: <86bk1kuajs.fsf@gnu.org> (raw)
In-Reply-To: <87le0pvzzj.fsf@laptop.lockywolf.net> (message from Lockywolf Laptop on Thu, 22 Aug 2024 14:06:53 +0800)

> From: Lockywolf Laptop <lockywolf@gmail.com>
> Cc: help-gnu-emacs@gnu.org, monnier@iro.umontreal.ca
> Date: Thu, 22 Aug 2024 14:06:53 +0800
> 
> >if the OOM mechanism of the OS kicks in while Emacs
> >still thinks it has more memory to use, it means something is wrong
> >with how the available memory is being reported to Emacs.  Emacs
> >should have sensed that it is approaching the limit and signaled the
> >memory-full signal before that happens.  I think this warrants a bug
> >report, with a reproducer.
> 
> Emacs doesn't actually crash or doesn't get killed because of OOM.
> Rather it produces a message of something like "Memory exhausted, run
> C-x C-s, and restart Emacs". Something does get broken at this point,
> as, for example, not all faces get rendered, but overall Emacs works.
> 
> I am not sure how how bad this is.

OK, it means at least Emacs knows about the memory problem and lets
you know, so you could end the session safely.

Thanks.



      reply	other threads:[~2024-08-22 10:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-20 10:26 Emacs on Android OOMs with pdf-tools. (And an Android howto.) Vladimir Nikishkin
2024-08-20 12:21 ` Stefan Monnier via Users list for the GNU Emacs text editor
2024-08-20 13:07   ` Po Lu
2024-08-22  0:50   ` Lockywolf
2024-08-22  4:22     ` Eli Zaretskii
2024-08-22  4:54     ` Po Lu
2024-08-22  6:06       ` Lockywolf Laptop
2024-08-22 10:16         ` Eli Zaretskii [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=86bk1kuajs.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@gnu.org \
    /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.