From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Gregory Heytings Newsgroups: gmane.emacs.bugs Subject: bug#57804: An infinite loop in a `fontify-region' function causes Emacs to hang indefinitely Date: Wed, 14 Sep 2022 17:34:10 +0000 Message-ID: <2b58b8f5429a6e3aecda@heytings.org> References: <87pmfx6h7y.fsf@gnus.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="34126"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Lars Ingebrigtsen , 57804@debbugs.gnu.org To: Paul Pogonyshev Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Sep 14 20:01:51 2022 Return-path: Envelope-to: geb-bug-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 1oYWhq-0008fW-CL for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 14 Sep 2022 20:01:50 +0200 Original-Received: from localhost ([::1]:50208 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oYWho-0004BX-KB for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 14 Sep 2022 14:01:48 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:40892) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oYWHu-0004XY-T8 for bug-gnu-emacs@gnu.org; Wed, 14 Sep 2022 13:35:08 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:39068) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oYWHu-0001kW-CE for bug-gnu-emacs@gnu.org; Wed, 14 Sep 2022 13:35:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oYWHu-0000fD-6C for bug-gnu-emacs@gnu.org; Wed, 14 Sep 2022 13:35:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Gregory Heytings Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 14 Sep 2022 17:35:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 57804 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: wontfix Original-Received: via spool by 57804-submit@debbugs.gnu.org id=B57804.16631768552488 (code B ref 57804); Wed, 14 Sep 2022 17:35:02 +0000 Original-Received: (at 57804) by debbugs.gnu.org; 14 Sep 2022 17:34:15 +0000 Original-Received: from localhost ([127.0.0.1]:55999 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oYWH9-0000e4-3q for submit@debbugs.gnu.org; Wed, 14 Sep 2022 13:34:15 -0400 Original-Received: from heytings.org ([95.142.160.155]:41206) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oYWH6-0000du-Mq for 57804@debbugs.gnu.org; Wed, 14 Sep 2022 13:34:13 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heytings.org; s=20220101; t=1663176851; bh=kh5Ofn81Awc+y0hpnPw7KkmFIZhVbVtPSutCVw0dkas=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References:From; b=3XFboDvvPTxIV5CHrShIqquL78dbJbDBukaoMYG07O9RWOnmj4iXSl3xSZvbhSKwP y2xqctNkfiC0dXTQD4lhKI3Llskb5Ms3uZa/w91XZ8RYV/vGeqI12aW60sofjYIYb9 2foY3RGAaFh8fzRFr4E3bd/cYDmX4oZYjvrJVasZ+4B8Wwmx7FAhlURps5JCCLHt6c 6r5pLhjaZ5gFn4BnCq/0Yq6HrJFAiUv3FpAEmHY0V3Dnl7+HEouebMdFcwdeQUp8Oh oPBEF3pHgYje9lvHL20F2NP5jUzp8Iels9EQV61Ax0cxtD7O1+19yonLjk4HXwMzDT AMuTNWWCCDgfg== In-Reply-To: X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:242505 Archived-At: > > E.g. in my case this happened in Logview mode, because it expected > `widen' to, well, widen, but Emacs `master' introduced half-cooked > narrowed locking that broke that expectation > Yes, master contains work in progress. If you want stable code, you should use the release branch. Note that the "fully cooked" narrowing will not magically solve that problem, though. Logview will have to be adapted to deal with the possibility of a locked narrowing. What you should most probably do in your case is to increase the value of long-line-threshold (or disable whatever causes Logview to infloop when locked narrowing is in effect, if that's feasible).