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#51336: 29.0.50; Application not responding Date: Sat, 13 Jan 2024 08:51:08 +0200 Message-ID: <83v87xhgkj.fsf@gnu.org> References: <67CF5E61-EE5A-4B24-9697-B61D75E67B4C@korins.ky> <87sfkvxqp4.fsf@gnus.org> <9F6E5B01-F80E-46AE-8A86-ED7080D09725@korins.ky> <1B89E5CF-789E-4DDE-8051-D7F22FA9D97B@korins.ky> <835y4r8w8a.fsf@gnu.org> <83cyuq6re1.fsf@gnu.org> <83a5paiflx.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="30893"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 51336@debbugs.gnu.org, alan@idiocy.org, stefankangas@gmail.com To: Kirill Korinsky Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Jan 13 07:52:10 2024 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 1rOXsI-0007oy-4o for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 13 Jan 2024 07:52:10 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rOXsC-0000XI-DH; Sat, 13 Jan 2024 01:52:04 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rOXsB-0000XA-J7 for bug-gnu-emacs@gnu.org; Sat, 13 Jan 2024 01:52:03 -0500 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1rOXsB-0004nl-AW for bug-gnu-emacs@gnu.org; Sat, 13 Jan 2024 01:52:03 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1rOXs9-00084b-N9 for bug-gnu-emacs@gnu.org; Sat, 13 Jan 2024 01:52:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 13 Jan 2024 06:52:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 51336 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: moreinfo Original-Received: via spool by 51336-submit@debbugs.gnu.org id=B51336.170512870331010 (code B ref 51336); Sat, 13 Jan 2024 06:52:01 +0000 Original-Received: (at 51336) by debbugs.gnu.org; 13 Jan 2024 06:51:43 +0000 Original-Received: from localhost ([127.0.0.1]:38222 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rOXrr-000846-9T for submit@debbugs.gnu.org; Sat, 13 Jan 2024 01:51:43 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:32788) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rOXrp-00083t-Pv for 51336@debbugs.gnu.org; Sat, 13 Jan 2024 01:51:42 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rOXrj-0004Xo-FZ; Sat, 13 Jan 2024 01:51:36 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=70+868vpayTP22sMDp/oapBnjQgqIT3Zotr/uTAqpTQ=; b=jXbAZpE0bBH4 S0Ib44ttaaiWyxVXCIVBybef8+wblAMscYRsUqlc9TkR6XCvvc51OCPVqqSbzKQu75J9d9stkPd8g FGXc58qDB78Hz0sy/VxnmMqXQokCpeRAy6IZJ3gcZicLWudvJsepS3F5Xw5NUpf110MGTbETosHnf NQrU7UATiyAUW6++B4QJEghGFzA9OibUM8HmG1JFV30kyRVHNxSMFMDIh1CHSxOfxVkIVdcbxjDft HdMjc3EfCG+W4IY6y+jb5h4niQRbMujNE2vzj/+5Ss9iVSjt0JxBnr5E+H+95qc4HQtm6Aqx0MLGU OqRN+8i3x08OkFB9PlQPXw==; In-Reply-To: (message from Kirill Korinsky on Sat, 13 Jan 2024 00:53:12 +0100) 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-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:278088 Archived-At: > Date: Sat, 13 Jan 2024 00:53:12 +0100 > From: Kirill Korinsky > > > > I'm confused: 6acb3c5b05a was installed on master, not on the > > > emacs-29 branch. AFAICT, Emacs 29 still has the code which that > > > commit removed. And yet the bug report is for Emacs 29(?). Am I > > > missing something? > > > > Kirill specified commit d9462e24a967e32d550ee886b5150f0cc78358f6 which > > is, I think, in the master branch. > > Yes, I usually runs on something from master which I pick each months or so. So the Emacs version where you see these freezes is 30.0.50, not 29.0.50 (or any other 29.x.y)? > During writing this email (~10 minutes?) it had frozen for a few seconds with > logs like this in *Message* buffer: > > Error during redisplay: (jit-lock-function 626) signaled (args-out-of-range "" 0) > Error during redisplay: (jit-lock-function 627) signaled (args-out-of-range "" 0) > Error during redisplay: (jit-lock-function 633) signaled (args-out-of-range "" 0) > Error during redisplay: (jit-lock-function 674) signaled (args-out-of-range "" 0) > Error during redisplay: (jit-lock-function 675) signaled (args-out-of-range "" 0) > Error during redisplay: (jit-lock-function 682) signaled (args-out-of-range "" 0) > Error during redisplay: (jit-lock-function 686) signaled (args-out-of-range "" 0) > Error during redisplay: (jit-lock-function 687) signaled (args-out-of-range "" 0) > Error during redisplay: (jit-lock-function 688) signaled (args-out-of-range "" 0) > Error during redisplay: (jit-lock-function 687) signaled (args-out-of-range "" 0) > Error during redisplay: (jit-lock-function 696) signaled (args-out-of-range "" 0) I would suggest to find out which Lisp code causes these messages. What mode do you use to type email, and what customizations of that mode do you have? Alan, is there something special in how redisplay on NS handles Lisp errors which happen in JIT font-lock? On other platforms, such errors are caught and ignored, resulting only in messages in *Messages*, they never cause any freezes, except perhaps for short time intervals (if the errors are generated at high frequency, or maybe continuously).