From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#45898: 27.1; wedged in redisplay again Date: Fri, 01 Jul 2022 09:04:19 +0300 Message-ID: <83y1xde5cs.fsf@gnu.org> References: <46b65e3f-cf3d-a3f2-9a9a-100e58274ff6@jovi.net> <83v8t6us8t.fsf@gnu.org> <87zgiinptk.fsf@gnus.org> <83mteiufih.fsf@gnu.org> <877d5kojbo.fsf@gnus.org> <83zgigu3e0.fsf@gnu.org> <500e4b9c69f2a90e7cf05b956178d71b@webmail.orcon.net.nz> <835yl3tnv3.fsf@gnu.org> <83iloyo0x7.fsf@gnu.org> <83mte5jukr.fsf@gnu.org> <837d57gbed.fsf@gnu.org> <83o7yicx3p.fsf@gnu.org> <83pmir5lwc.fsf@gnu.org> <83mtdu68cl.fsf@gnu.org> <837d4yf18n.fsf@gnu.org> <6A3A8E3E-9FF6-4509-893B-EBFF7B573CDA@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="19594"; mail-complaints-to="usenet@ciao.gmane.io" Cc: psainty@orcon.net.nz, larsi@gnus.org, Emacs-hacker2018@jovi.net, monnier@iro.umontreal.ca, 45898@debbugs.gnu.org To: Gerd =?UTF-8?Q?M=C3=B6llmann?= Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Jul 01 08:05:12 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 1o79mA-0004u5-Vy for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 01 Jul 2022 08:05:11 +0200 Original-Received: from localhost ([::1]:36680 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1o79mA-0005ng-0Z for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 01 Jul 2022 02:05:10 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:39044) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o79m2-0005nX-B8 for bug-gnu-emacs@gnu.org; Fri, 01 Jul 2022 02:05:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:42225) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1o79m2-0007yD-1q for bug-gnu-emacs@gnu.org; Fri, 01 Jul 2022 02:05:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1o79m1-0005nd-S1 for bug-gnu-emacs@gnu.org; Fri, 01 Jul 2022 02:05:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 01 Jul 2022 06:05:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 45898 X-GNU-PR-Package: emacs Original-Received: via spool by 45898-submit@debbugs.gnu.org id=B45898.165665546822247 (code B ref 45898); Fri, 01 Jul 2022 06:05:01 +0000 Original-Received: (at 45898) by debbugs.gnu.org; 1 Jul 2022 06:04:28 +0000 Original-Received: from localhost ([127.0.0.1]:36122 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1o79lQ-0005mg-Ai for submit@debbugs.gnu.org; Fri, 01 Jul 2022 02:04:28 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:53916) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1o79lL-0005mQ-DH for 45898@debbugs.gnu.org; Fri, 01 Jul 2022 02:04:22 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:43036) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o79lE-0005rw-Nv; Fri, 01 Jul 2022 02:04:12 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=M8s4HZ5zWBP9ztEmvTaQkaJlcgO9YG96DiQbNjzRDA0=; b=eol4sWdwWA1A6kVHf1tq qpEz+AtBUw6drgRucgUWlLxoFnmzqfKi6v+nBrw6tfz22I11fmO7+GF309105mKJBNfnAHf9HCFrq +nAet0kYXj+smlXbfYaD2uqf8I6u/XW3WO4hX5DdnRJDLwLv58WrgmdK4jcEktGdmC1g/uiBPcwzn dexQn9KXT7dED03WFhXvnF6fJR0mKqJ8PoJYmDFELj2QQN4PDq/4+y9m+2Co8TCy2hit5gXUgUcf8 +szsDN5MrA30NPojVvLBQ5bb5DiiZ2J4j8q/HFK4KG9MVdlRrAh+0Eht8s6K1ceNFSEjyE9MYqqjj D88sHcYSoJX2IQ==; Original-Received: from [87.69.77.57] (port=3619 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1o79lB-0003fN-W5; Fri, 01 Jul 2022 02:04:12 -0400 In-Reply-To: <6A3A8E3E-9FF6-4509-893B-EBFF7B573CDA@gmail.com> (message from Gerd =?UTF-8?Q?M=C3=B6llmann?= on Fri, 1 Jul 2022 06:42:23 +0200) 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:235763 Archived-At: > From: Gerd Möllmann > Date: Fri, 1 Jul 2022 06:42:23 +0200 > Cc: Eli Zaretskii , > larsi@gnus.org, > psainty@orcon.net.nz, > Emacs-hacker2018@jovi.net, > 45898@debbugs.gnu.org > > > [1:text/plain Hide] > > > > On 2022-06-30,, at 21:56 , Stefan Monnier wrote: > > > >>> Unsuprisingly so: none of `C-n/C-p/C-v/...` involve font-lock or > >>> jit-lock either during their operation or during the > >>> subsequent redisplay phase in the current code: the one-line is all > >>> fontified once and for all when you open the file and after that > >>> font-lock is not involved any more (until you make an edit, that is). > >> > >> That's only true if max-redisplay-ticks is zero. > > > > Why would that make a difference? When I try `master` with this set to > > 100000, the file still shows up with font-locking, so apparently it's > > been fully font-locked despite `max-redisplay-ticks` and after that > > font-locking (and syntax-propertize) won't make any difference any more > > (until the buffer is edited) since they're already done. > > [ Of course font-locking (and syntax-propertize) still do have an > > effect in that the text-properties they applied can impact the time it > > takes for the redisplay to do its job; so by "won't make any difference" > > I mean that 0-cycles will be spent running font-lock of > > syntax-propertize code. ] > > Would it be possible to run this with gprof profiling? I think that could give some clues what is going on. Or (on GNU/Linux only) under 'prof' -- which doesn't require you to build a special version of Emacs, and still produces detailed CPU usage info.