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#57207: 29.0.50; Fontification is slow after e7b5912b23 (Improvements to long lines handling) Date: Tue, 16 Aug 2022 12:24:44 +0000 Message-ID: <325f95fd2bca916950fe@heytings.org> References: <87bksmx1j1.fsf@localhost> <5900f208367791fbdfe2@heytings.org> <83bksmka08.fsf@gnu.org> <325f95fd2b7c0cc80613@heytings.org> <83y1voflmb.fsf@gnu.org> <87wnb81izs.fsf@localhost> 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="7618"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Eli Zaretskii , 57207@debbugs.gnu.org To: Ihor Radchenko Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Aug 16 14:25:25 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 1oNvdM-0001oQ-EB for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 16 Aug 2022 14:25:24 +0200 Original-Received: from localhost ([::1]:41106 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oNvdL-0003uZ-Ef for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 16 Aug 2022 08:25:23 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:51392) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oNvd1-0003uN-DH for bug-gnu-emacs@gnu.org; Tue, 16 Aug 2022 08:25:04 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:55428) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oNvd0-0001GY-8w for bug-gnu-emacs@gnu.org; Tue, 16 Aug 2022 08:25:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oNvcz-00080U-Rg for bug-gnu-emacs@gnu.org; Tue, 16 Aug 2022 08:25:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Gregory Heytings Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 16 Aug 2022 12:25:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 57207 X-GNU-PR-Package: emacs Original-Received: via spool by 57207-submit@debbugs.gnu.org id=B57207.166065268830752 (code B ref 57207); Tue, 16 Aug 2022 12:25:01 +0000 Original-Received: (at 57207) by debbugs.gnu.org; 16 Aug 2022 12:24:48 +0000 Original-Received: from localhost ([127.0.0.1]:45177 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oNvcm-0007zw-DX for submit@debbugs.gnu.org; Tue, 16 Aug 2022 08:24:48 -0400 Original-Received: from heytings.org ([95.142.160.155]:55726) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oNvck-0007zn-6j for 57207@debbugs.gnu.org; Tue, 16 Aug 2022 08:24:46 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heytings.org; s=20220101; t=1660652685; bh=IUci4ZDsVljmPiwXvciSp9sLMVaSehpOy8T5GD//yWw=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References:From; b=TVu5DwGtncSThcUw3kfNW1LrF4RlQIUgJHsfLt8yJ/ovevXTDtOtcF7Qw7Dqg3Lik AELLz4Zj8An7J7mVGcJfE/mgMD/uHocbE36WCT6pB4ifBuHMUqV1fPaujFXJLICmEc ccqJaLx9zl9W53JRS2UNU5w7m31iE8qkcuqeVV4K1UjKrkNplRGOD89IZKtxOgjKXn u7NOGyv39Eap7uyjgdjkjKREsZ8XEHTM8kqfqWWAFKFXhF1DObaqOZeJeDN2uGomsa z8BmKPvSTOtLmmkK8/JHGcW9eyzc81Zrt83gtRbmxzbwPJXVydRMukic9M+TT84SqP vxFsOdEy7N50w== In-Reply-To: <87wnb81izs.fsf@localhost> 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:239909 Archived-At: > > Clarification: I was unable to trigger the hang again. I am not sure > what I did the first time (I played with long-line-threshold values > inside the same Org buffer), > That wouldn't work (or at least it might not do what you expect): once a too long line has been found in the buffer the long line optimizations are enabled, and long lines are not detected anymore. > > but I suspect that there were also some errors raised in the Org > fontification code - parts of the buffer got wrong fontification just > before the hang. Of course, these errors are probably also an indication > that something is going wrong, but the hang may not be directly related > to the slowdown. > > Throughout my today's attempts to reproduce, I did not see any obvious > difference in the slowdown between 10000 and 100000 long-line-threshold > values. > Okay, so my guess is that it's in fact something in the Org fontification code which infloops when locked narrowing is enabled.