From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: "memory full" during redisplay Date: Wed, 10 Dec 2014 18:10:17 +0200 Message-ID: <83mw6vv63a.fsf@gnu.org> References: <838uigwv8b.fsf@gnu.org> <54877744.4050902@cs.ucla.edu> <83tx14uq4h.fsf@gnu.org> <5487EC98.7000409@cs.ucla.edu> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1418227861 25632 80.91.229.3 (10 Dec 2014 16:11:01 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 10 Dec 2014 16:11:01 +0000 (UTC) Cc: emacs-devel@gnu.org To: Paul Eggert Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Dec 10 17:10:54 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Xyjqn-0000li-K5 for ged-emacs-devel@m.gmane.org; Wed, 10 Dec 2014 17:10:53 +0100 Original-Received: from localhost ([::1]:46481 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xyjqn-0002WJ-2G for ged-emacs-devel@m.gmane.org; Wed, 10 Dec 2014 11:10:53 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:49778) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XyjqW-0002P7-DD for emacs-devel@gnu.org; Wed, 10 Dec 2014 11:10:41 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XyjqR-0006l2-8G for emacs-devel@gnu.org; Wed, 10 Dec 2014 11:10:36 -0500 Original-Received: from mtaout23.012.net.il ([80.179.55.175]:45494) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XyjqR-0006hf-0g for emacs-devel@gnu.org; Wed, 10 Dec 2014 11:10:31 -0500 Original-Received: from conversion-daemon.a-mtaout23.012.net.il by a-mtaout23.012.net.il (HyperSendmail v2007.08) id <0NGD00000JDU2200@a-mtaout23.012.net.il> for emacs-devel@gnu.org; Wed, 10 Dec 2014 18:10:29 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout23.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NGD00ND3JL84M60@a-mtaout23.012.net.il>; Wed, 10 Dec 2014 18:10:29 +0200 (IST) In-reply-to: <5487EC98.7000409@cs.ucla.edu> X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 X-Received-From: 80.179.55.175 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:179663 Archived-At: > Date: Tue, 09 Dec 2014 22:47:52 -0800 > From: Paul Eggert > CC: emacs-devel@gnu.org > > Eli Zaretskii wrote: > > Because that memory reserve is not enough in the use cases I'm talking > > about. The code needs more than just that reserve. > > How about if we reserve more memory? That should be a simple change. How will we know how much to reserve? Eventually, there could be a request for more than we reserved, and we are back to square one.