From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: "Jay Berkenbilt" Newsgroups: gmane.emacs.bugs Subject: bug#55726: 28.1; emacs becomes unresponsive to input Date: Mon, 30 May 2022 11:18:01 -0400 Message-ID: <49de370b-6c5b-4bd0-a998-4683d6103995@www.fastmail.com> References: <11874f4a-5f7c-4f88-923f-4a6310654697@www.fastmail.com> <83fskrjf6p.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="16213"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Cyrus-JMAP/3.7.0-alpha0-591-gfe6c3a2700-fm-20220427.001-gfe6c3a27 To: 55726@debbugs.gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon May 30 17:26:31 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 1nvhHq-00041h-Br for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 30 May 2022 17:26:30 +0200 Original-Received: from localhost ([::1]:52842 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nvhHp-00054J-C8 for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 30 May 2022 11:26:29 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:56160) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nvhAc-00034c-MN for bug-gnu-emacs@gnu.org; Mon, 30 May 2022 11:19:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:51870) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nvhAc-0007eO-CG for bug-gnu-emacs@gnu.org; Mon, 30 May 2022 11:19:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1nvhAc-0003u0-52 for bug-gnu-emacs@gnu.org; Mon, 30 May 2022 11:19:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: "Jay Berkenbilt" Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 30 May 2022 15:19:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 55726 X-GNU-PR-Package: emacs Original-Received: via spool by 55726-submit@debbugs.gnu.org id=B55726.165392391114925 (code B ref 55726); Mon, 30 May 2022 15:19:02 +0000 Original-Received: (at 55726) by debbugs.gnu.org; 30 May 2022 15:18:31 +0000 Original-Received: from localhost ([127.0.0.1]:45767 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nvhA7-0003sf-5A for submit@debbugs.gnu.org; Mon, 30 May 2022 11:18:31 -0400 Original-Received: from wout5-smtp.messagingengine.com ([64.147.123.21]:41611) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nvhA4-0003sQ-Rm for 55726@debbugs.gnu.org; Mon, 30 May 2022 11:18:29 -0400 Original-Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id E9C993200657 for <55726@debbugs.gnu.org>; Mon, 30 May 2022 11:18:22 -0400 (EDT) Original-Received: from imap49 ([10.202.2.99]) by compute4.internal (MEProxy); Mon, 30 May 2022 11:18:23 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ql.org; h=cc :content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm1; t=1653923902; x=1654010302; bh=NY+QIH0W8M 0CyFmUigCSgZ9EdZLOBFqRN/tfW4AMnto=; b=F3PAlanmE1I78WrG7bvqMXpS4w aVn28Wn87vy05SPLvU4ViBcQAKfu/LbIp/9yN7RLMv//RWVG4N+l/lGBPY+uzr/F LIrNvR7J9JwHPFSBpHbRdhoSmctRlJ5O/dEKwdgbtV0+BIrI0tAfCct478NnZJqa HD+78UiJg1VQPoqkJDeDl1NY4VtM7yHWgLl5bEqwIiPLEwb+BuLQ1t9rsKrcCo6K 7b+L5MtA7qZ4UY+IU63foQxANFP7JRYgTWz24n5qn3qmq9USwyZ4ZlxiRZBXWqHf ntQzuz+wiP5khXsf+IIFbisYrY5QBlCqI90PgTTGilGtXh4JR+meUxhom8kg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:date:feedback-id :feedback-id:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to :x-me-proxy:x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s= fm1; t=1653923902; x=1654010302; bh=NY+QIH0W8M0CyFmUigCSgZ9EdZLO BFqRN/tfW4AMnto=; b=BcpCZDTlpr6orB4Ked9Rt+LP9uLPfmc4TFnKPnxK7PJU qYnWs5q9qyGYXkR3ENxMTT4jimK5+4C9yo3xTvRwLRYGFWV2dXJOzcbIiMCOUDwI XHUEnLol4yL8rieLJUBQEbtQe6PrzTVxF8iaX+NKpFaQ3ob4cxV79A5I+AGkUh36 kfwRiaWj7jwXclgPx3rV8htifV9jqTnFMWOHABsAR4H1EdNEAc0eC4koN5NZU+13 AEnsQlO0iNiyyrJrNisxAIcY5Q5S3qM4ONtlXC/PqC0EiGJAd8a4MfjFegq0qjQ8 ioO+aX+VoLclJ9TpAxeRpxDbPgfQB0/LTb3P8CERNQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvfedrkeeigdekfecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesthdtre dtreertdenucfhrhhomhepfdflrgihuceuvghrkhgvnhgsihhlthdfuceovghjsgesqhhl rdhorhhgqeenucggtffrrghtthgvrhhnpeehtdevhfefvdffgfeifeduheefhfduhfegff fgffdtveelffehvddvheejffeukeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgr mhepmhgrihhlfhhrohhmpegvjhgssehqlhdrohhrgh X-ME-Proxy: Feedback-ID: ibd3147ef:Fastmail Original-Received: by mailuser.nyi.internal (Postfix, from userid 501) id 2F39315A0080; Mon, 30 May 2022 11:18:22 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface 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:233386 Archived-At: oops -- accidentally left bug address off my previous reply... On Mon, May 30, 2022, at 9:57 AM, Eli Zaretskii wrote: > > Cc: ejb@ql.org > > Date: Mon, 30 May 2022 08:58:26 -0400 > > From: "Jay Berkenbilt" > > >> . . . > > > > My emacs is built from source using default configure options, so I was > > able to attach my running emacs process in gdb and get a stack trace. > > Here is the stack trace: > > > > . . . > > This says that Emacs's main thread is just waiting for input, either > from the keyboard or from any other sources, like the window-system or > subprocesses. > > If this session is still alive under GDB, please type this command: > > (gdb) thread apply all bt > > and show the output -- it will tell us what the other threads are > doing. If you already killed that session, then do the above next > time it happens. I will do it next time it happens. Thanks. > It is also important to know whether Emacs is stuck or inflooping. Do > you happen to know if it was using the CPU while in this state? The > strategy to dig into the problem depends on whether Emacs hangs (which > might mean some kind of deadlock), or infloops in some code. I don't think the CPU was spinning, but I can't guarantee. I will also check this the next time it happens. > > Load-path shadows: > > /home/ejb/elisp/startup hides /usr/local/emacs-28.1/share/emacs/28.1/lisp/startup > > Did you build your own Emacs, and if so, is it possible that this > startup.el, which shadows the standard one, was dumped into the > executable? If so, it could be part of the puzzle. I don't think it is. My elisp/startup.el defines a function called "qstartup". If I run emacs -Q, (fboundp 'qstartup) is nil, and if I run with my environment, (fboundp qstartup) is t. Anyway, I don't think there's anything in the build process that would read my .emacs, and my .emacs has been loading ~/elisp/startup.el for decades. I'm not aware of this ever having caused a problem, but I could consider renaming the file. I'll wait to make that change until I have a reliable way to reproduce the problem. Thanks -- this is definitely something to account for.