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#50284: 28.0.50; Emacs crashes occasionally on macOS BigSur Date: Tue, 31 Aug 2021 14:59:49 +0300 Message-ID: <83lf4hu8ne.fsf@gnu.org> References: Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="6201"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 50284@debbugs.gnu.org To: Umar Ahmad Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Aug 31 14:02:01 2021 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 1mL2Sm-0001IA-NT for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 31 Aug 2021 14:02:00 +0200 Original-Received: from localhost ([::1]:39166 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mL2Sk-0003cr-Af for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 31 Aug 2021 08:01:58 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:55942) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mL2Rt-00037N-9p for bug-gnu-emacs@gnu.org; Tue, 31 Aug 2021 08:01:05 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:49882) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1mL2Rp-0005SS-N5 for bug-gnu-emacs@gnu.org; Tue, 31 Aug 2021 08:01:05 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1mL2Rp-00085k-Le for bug-gnu-emacs@gnu.org; Tue, 31 Aug 2021 08:01: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: Tue, 31 Aug 2021 12:01:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 50284 X-GNU-PR-Package: emacs Original-Received: via spool by 50284-submit@debbugs.gnu.org id=B50284.163041120530969 (code B ref 50284); Tue, 31 Aug 2021 12:01:01 +0000 Original-Received: (at 50284) by debbugs.gnu.org; 31 Aug 2021 12:00:05 +0000 Original-Received: from localhost ([127.0.0.1]:33195 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mL2Qu-00083R-RD for submit@debbugs.gnu.org; Tue, 31 Aug 2021 08:00:05 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:39620) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mL2Qr-00082D-4w for 50284@debbugs.gnu.org; Tue, 31 Aug 2021 08:00:03 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:60092) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mL2Ql-0004pz-On; Tue, 31 Aug 2021 07:59:55 -0400 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:3001 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 1mL2Qk-000581-HD; Tue, 31 Aug 2021 07:59:55 -0400 In-Reply-To: (bug-gnu-emacs@gnu.org) 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:213092 Archived-At: > Date: Tue, 31 Aug 2021 01:08:17 +0530 > From: Umar Ahmad via "Bug reports for GNU Emacs, > the Swiss army knife of text editors" > > I haven't been able to reproduce this considering emacs crashes > in maybe once a week or so but it usually happens while opening a file > in a new project. I have lsp-mode enabled, so that can be a possible > cause here, considering that is probably the only extra thing that > initializes when opening the file in the new project. > > I've installed Emacs through the brew formula hosted at > https://github.com/d12frosted/homebrew-emacs-plus > > The command used was: > brew install emacs-plus@28 --with-xwidgets --with-native-comp Thank you for your report. > Thread 0 Crashed:: Dispatch queue: com.apple.main-thread > 0 libsystem_kernel.dylib 0x00007fff203e192e __pthread_kill + 10 > 1 libsystem_pthread.dylib 0x00007fff204105bd pthread_kill + 263 > 2 libsystem_c.dylib 0x00007fff202f4bd5 raise + 26 > 3 org.gnu.Emacs 0x000000010f646922 terminate_due_to_signal + 167 > 4 org.gnu.Emacs 0x000000010f647021 emacs_abort + 15 > 5 org.gnu.Emacs 0x000000010f612b5a ns_term_shutdown + 119 > 6 org.gnu.Emacs 0x000000010f5267ce shut_down_emacs + 339 > 7 org.gnu.Emacs 0x000000010f6468f0 terminate_due_to_signal + 117 > 8 org.gnu.Emacs 0x000000010f54078c handle_fatal_signal + 14 > 9 org.gnu.Emacs 0x000000010f5407fe deliver_thread_signal + 114 > 10 org.gnu.Emacs 0x000000010f53f2aa deliver_fatal_thread_signal + 9 > 11 libsystem_platform.dylib 0x00007fff20455d7d _sigtramp + 29 > 12 ??? 0x0000000000001e99 0 + 7833 > 13 libsystem_c.dylib 0x00007fff20365406 abort + 125 > 14 org.gnu.Emacs 0x000000010f56f396 re_match_2_internal + 17627 We need to know where in regex-emacs.c is the place shown in the last line above. Can you try establishing that? > 15 org.gnu.Emacs 0x000000010f56ac4e rpl_re_search_2 + 2634 > 16 org.gnu.Emacs 0x000000010f56a1fe rpl_re_search + 37 > 17 org.gnu.Emacs 0x000000010f563c00 string_match_1 + 406 > 18 org.gnu.Emacs 0x000000010f598e0c funcall_subr + 292 > 19 org.gnu.Emacs 0x000000010f5986a3 Ffuncall + 660 > 20 s-aaf786a9-6de971fe.eln 0x0000000169c69e50 F732d6d6174636865733f_s_matches_0 + 128 This indicates that you are using s.el, which makes tracking this bug harder. > 21 org.gnu.Emacs 0x000000010f59919e funcall_lambda + 682 > 22 org.gnu.Emacs 0x000000010f59919e funcall_lambda + 682 > 23 org.gnu.Emacs 0x000000010f59919e funcall_lambda + 682 > <-- truncated - same line repeated 488 times --> > 511 org.gnu.Emacs 0x000000010f59919e funcall_lambda + 682 And this seems to indicate a possible infinite recursion in some Lisp program you were running. So I think we need to see the full Lisp backtrace when this happens, or at least the Lisp code which runs.