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 07:22:35 +0300 Message-ID: <86o75ltcdw.fsf@gnu.org> References: <8734mxxtwd.fsf@laptop.lockywolf.net> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="15335"; 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 06:23:10 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 1sgzLq-0003p5-Hg for geh-help-gnu-emacs@m.gmane-mx.org; Thu, 22 Aug 2024 06:23:10 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sgzLM-000673-35; Thu, 22 Aug 2024 00:22:40 -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 1sgzLJ-00066r-KY for help-gnu-emacs@gnu.org; Thu, 22 Aug 2024 00:22:37 -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 1sgzLJ-0002Fy-0p for help-gnu-emacs@gnu.org; Thu, 22 Aug 2024 00:22:37 -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=iqccjgqdTYyk46txauQOqkTdFvfkHjLjiAQmN1tnrzo=; b=j5PU1CtUVQUc 1CHjIwNkAf1kQlbsKWWLukpQ4yQ12ZTmGkbfZvXPsJm/KMa2c5YU8v0M23tpfN7qk7E46Z/XYovRp uzq7V8JnIiiiXhC7tefD4eKP1+GqN813Cru1sh3gUbMSLJgZY6CwZYP5YeCGnEh4JNGGuvEKgYChI 2MwzDX7GbYiZ1JMT+jvGmlUxDX0ZbQ4UdywBN2JDpZrMsBP4msjauXGLUjDXUV/8hclE5wlUuJmk7 i2OziS1mJf8AhcqFgC9IAgXoos1JTG57czvhG+3cWOaG32ce/0AnRMQzjYX4tmxxsWns1oNrEhkbG 7Y8exfaCVEa+hRrXzLCZfA==; In-Reply-To: <8734mxxtwd.fsf@laptop.lockywolf.net> (message from Lockywolf on Thu, 22 Aug 2024 08:50:42 +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:147749 Archived-At: > From: Lockywolf > Date: Thu, 22 Aug 2024 08:50:42 +0800 > > Is it possible to tell Emacs to not generate so much cache? Try playing with the value of image-cache-eviction-delay. But how did you get to so many images? what images are they and what did you do in Emacs to have them all loaded? Emacs is not meant to be used with so many images on a device that has such severe memory limitations. More importantly, 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.