From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Tassilo Horn Newsgroups: gmane.emacs.devel Subject: Re: Progress on bug#3521? mode-line updates break process-send-region Date: Sun, 28 Jun 2009 22:39:18 +0200 Message-ID: <87my7sgkjt.fsf@thinkpad.tsdh.de> References: <87tz20y9lb.fsf@thinkpad.tsdh.de> <87iqigjtoj.fsf@stupidchicken.com> <873a9kic7r.fsf@thinkpad.tsdh.de> <87d48ofijv.fsf@stupidchicken.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1246221580 14572 80.91.229.12 (28 Jun 2009 20:39:40 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 28 Jun 2009 20:39:40 +0000 (UTC) Cc: Chong Yidong , emacs-devel@gnu.org, 3521@emacsbugs.donarmstrong.com To: Andreas Schwab Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Jun 28 22:39:32 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1ML19w-00043O-75 for ged-emacs-devel@m.gmane.org; Sun, 28 Jun 2009 22:39:32 +0200 Original-Received: from localhost ([127.0.0.1]:47559 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ML19v-00067Y-Hf for ged-emacs-devel@m.gmane.org; Sun, 28 Jun 2009 16:39:31 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1ML19p-00066v-Na for emacs-devel@gnu.org; Sun, 28 Jun 2009 16:39:25 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1ML19m-000669-2u for emacs-devel@gnu.org; Sun, 28 Jun 2009 16:39:25 -0400 Original-Received: from [199.232.76.173] (port=47568 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1ML19l-000666-RR for emacs-devel@gnu.org; Sun, 28 Jun 2009 16:39:21 -0400 Original-Received: from out2.smtp.messagingengine.com ([66.111.4.26]:58876) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1ML19l-0007Ax-E8 for emacs-devel@gnu.org; Sun, 28 Jun 2009 16:39:21 -0400 Original-Received: from compute2.internal (compute2.internal [10.202.2.42]) by out1.messagingengine.com (Postfix) with ESMTP id 0F3F137E20A; Sun, 28 Jun 2009 16:39:21 -0400 (EDT) Original-Received: from heartbeat2.messagingengine.com ([10.202.2.161]) by compute2.internal (MEProxy); Sun, 28 Jun 2009 16:39:21 -0400 X-Sasl-enc: khVWod/u69PcaE0pmjKYA1O+ZwPR2Yincz9VkifXLNNF 1246221560 Original-Received: from thinkpad.tsdh.de (p54AF372D.dip0.t-ipconnect.de [84.175.55.45]) by mail.messagingengine.com (Postfix) with ESMTPA id 3611E3D5D6; Sun, 28 Jun 2009 16:39:18 -0400 (EDT) Mail-Copies-To: never In-Reply-To: (Andreas Schwab's message of "Sun, 28 Jun 2009 22:15:00 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (gnu/linux) X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:111790 Archived-At: Andreas Schwab writes: Hi Andreas, >> On my 32-bit machine, the error occurs earlier. But If I insert an >> `erase-buffer' call into your loop, so that the size of the temporary >> buffer is bounded, Emacs completes the 999999-iteration loop without >> any error. > > The whole point of the test case is the big size of the buffer string. > This is a typical symptom of a GC bug. I have checked in a fix. Wow, this was quick. Tomorrow, I'll test it and report back if the bug is gone. Chong wrote: > If there's any connection with mode-line updates, I have not been able > to reproduce it. I already reported the bug as #2272, and Andreas checked in a fix for it. At that time, I couldn't reproduce it, but out of sudden, it hit me again, and David Engster found out that it seems to be triggered when the mode-line is updated. He got the error because of `display-time' and I got it when `rcirc-track-minor-mode' updated the mode-line. So since Andreas last fix, the update of the mode-line was needed for me to trigger the bug again. Bye, Tassilo