From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.help Subject: Re: Emacs on Android OOMs with pdf-tools. (And an Android howto.) Date: Thu, 22 Aug 2024 13:16:55 +0300 Message-ID: <86bk1kuajs.fsf@gnu.org> References: <8734mxxtwd.fsf@laptop.lockywolf.net> <87a5h5f97k.fsf@yahoo.com> <87le0pvzzj.fsf@laptop.lockywolf.net> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="6286"; mail-complaints-to="usenet@ciao.gmane.io" To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Thu Aug 22 12:17:38 2024 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1sh4ss-0001VS-3I for geh-help-gnu-emacs@m.gmane-mx.org; Thu, 22 Aug 2024 12:17:38 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sh4sI-0007Lp-Cy; Thu, 22 Aug 2024 06:17:02 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sh4sF-0007LW-NF for help-gnu-emacs@gnu.org; Thu, 22 Aug 2024 06:17:00 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sh4sF-0005TH-EK for help-gnu-emacs@gnu.org; Thu, 22 Aug 2024 06:16:59 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=zZhDJMBdrr0yVhjxvqfBhKybm9Up6M8KK3/KnR6ensw=; b=En7YH1n4baCQ JxWkgu1giYWFgxTssnKUB8J3zg/1VvFyx1DP3C8PYfI/f/Ms//mY+pbQa2HHItJ9vOs9fMimJNdYB 0qoONjnOSbg6qemShnkbF826iAna5otsLMp6tM4PVpX1bly1S7ov05ViJAph1pQSaOPrJSen7dwEB IxntM7Gfg8VZTw3io1p2cuD377HY+Rqk4vU9JSOYcjeFO1NHRujMY+PBc4T78grB+EvvXzpOfa9i5 XIcN1sQJqWM/ZLLYWl8GufTpG94+EHWHOjU9Ct4Bo/eY+yI0DZ5iiQ3AJDYFMsUlPl9rmvNMvARnf s0CKRuAvNkWbl5BdVxrimg==; In-Reply-To: <87le0pvzzj.fsf@laptop.lockywolf.net> (message from Lockywolf Laptop on Thu, 22 Aug 2024 14:06:53 +0800) X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.help:147756 Archived-At: > From: Lockywolf Laptop > 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.