From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Chong Yidong Newsgroups: gmane.emacs.devel Subject: Re: emacs hangs in jit-lock Date: Tue, 28 Nov 2006 15:03:06 -0500 Message-ID: <87k61fibk5.fsf@stupidchicken.com> References: <456C70A0.6060105@gnu.org> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1164744504 24568 80.91.229.2 (28 Nov 2006 20:08:24 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 28 Nov 2006 20:08:24 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Nov 28 21:08:21 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1Gp9FK-0008PO-Hn for ged-emacs-devel@m.gmane.org; Tue, 28 Nov 2006 21:08:02 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Gp9FK-0002sz-5M for ged-emacs-devel@m.gmane.org; Tue, 28 Nov 2006 15:08:02 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Gp9AO-000839-UH for emacs-devel@gnu.org; Tue, 28 Nov 2006 15:02:57 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Gp9AN-00081t-Dg for emacs-devel@gnu.org; Tue, 28 Nov 2006 15:02:55 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Gp9AN-00081Q-2w for emacs-devel@gnu.org; Tue, 28 Nov 2006 15:02:55 -0500 Original-Received: from [18.19.1.138] (helo=cyd.mit.edu) by monty-python.gnu.org with esmtp (Exim 4.52) id 1Gp9AL-0003jf-MX; Tue, 28 Nov 2006 15:02:53 -0500 Original-Received: by cyd.mit.edu (Postfix, from userid 1000) id B49EC4E43B; Tue, 28 Nov 2006 15:03:06 -0500 (EST) Original-To: Sam Steingold In-Reply-To: <456C70A0.6060105@gnu.org> (Sam Steingold's message of "Tue\, 28 Nov 2006 12\:23\:44 -0500") User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.91 (gnu/linux) 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:62986 Archived-At: Sam Steingold writes: > "line-end-position" (0x29e02) > "back-to-indentation" (0x2e0) > "c-beginning-of-macro" (0x27bda8) > "byte-code" (0xa5c7eab) > "c-parse-state" (0x27bda8) > "c-font-lock-complex-decl-prepare" (0x27d0b8) > "font-lock-fontify-keywords-region" (0x27bda8) > "font-lock-default-fontify-region" (0x27bda8) > "font-lock-fontify-region" (0x27bda8) > "run-hook-with-args" (0x840af31) > "byte-code" (0x822f25b) > "jit-lock-fontify-now" (0x27bed8) > "jit-lock-stealth-fontify" (0x83178f9) > > the problem is that this unresponsiveness can last for MINUTES (I am not > making this up!) and the periods of responsiveness can last for mere > SECONDS. > > Even if it should, any input from me should immediately interrupt it - > and I see my C-g "delayed" for minutes. Since jit-lock-stealth fontify is run as an idle timer, any input *does* interrupt it. The only way this could fail is if the c-font-lock functions interfere with this---either by somehow resetting the idleness state, or (more likely) taking a very long time. If you provided a simple test case, I or someone else could take a look at this problem.