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: "memory full" during redisplay Date: Tue, 09 Dec 2014 20:09:40 +0200 Message-ID: <838uigwv8b.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1418148616 11755 80.91.229.3 (9 Dec 2014 18:10:16 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 9 Dec 2014 18:10:16 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Dec 09 19:10:09 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 1XyPEf-0000lJ-GG for ged-emacs-devel@m.gmane.org; Tue, 09 Dec 2014 19:10:09 +0100 Original-Received: from localhost ([::1]:41751 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XyPEe-0004t2-VW for ged-emacs-devel@m.gmane.org; Tue, 09 Dec 2014 13:10:08 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:50619) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XyPET-0004qv-QK for emacs-devel@gnu.org; Tue, 09 Dec 2014 13:10:06 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XyPEK-0004wC-Gi for emacs-devel@gnu.org; Tue, 09 Dec 2014 13:09:57 -0500 Original-Received: from mtaout22.012.net.il ([80.179.55.172]:65459) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XyPEK-0004uo-95 for emacs-devel@gnu.org; Tue, 09 Dec 2014 13:09:48 -0500 Original-Received: from conversion-daemon.a-mtaout22.012.net.il by a-mtaout22.012.net.il (HyperSendmail v2007.08) id <0NGB00K00U9Y3400@a-mtaout22.012.net.il> for emacs-devel@gnu.org; Tue, 09 Dec 2014 20:09:46 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout22.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NGB00G1MUGAR170@a-mtaout22.012.net.il> for emacs-devel@gnu.org; Tue, 09 Dec 2014 20:09:46 +0200 (IST) X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 X-Received-From: 80.179.55.172 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:179583 Archived-At: While investigating bug #19322, I found out that memory-allocation functions called in a few places during redisplay will signal a memory-full error when there's not enough free memory to satisfy a request. However, signaling an error in the middle of redisplay is not a good idea, because Emacs will immediately re-enter redisplay, again signal an error, etc. This causes Emacs to lock hard, and the only thing the user can do is forcibly terminate the process. So I think we should modify memory_full to handle this differently during redisplay. Do we already have some machinery for this, or do we need to invent something new?