From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eric Abrahamsen Newsgroups: gmane.emacs.bugs Subject: bug#52735: 29.0.50; Gnus hangs while getting new news Date: Wed, 22 Dec 2021 08:23:35 -0800 Message-ID: <87a6gsa9rs.fsf@ericabrahamsen.net> References: <87sfukekpo.fsf@gmx.net> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="31661"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) To: 52735@debbugs.gnu.org Cancel-Lock: sha1:tZrSvu9oHfXXfGFNhOCXgscmjus= Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed Dec 22 17:24:14 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 1n04PW-00082R-Lj for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 22 Dec 2021 17:24:14 +0100 Original-Received: from localhost ([::1]:44036 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1n04PU-0002EU-Kp for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 22 Dec 2021 11:24:12 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:59558) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n04PL-0002EE-OK for bug-gnu-emacs@gnu.org; Wed, 22 Dec 2021 11:24:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:48039) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1n04PK-0004RI-Ej for bug-gnu-emacs@gnu.org; Wed, 22 Dec 2021 11:24:03 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1n04PK-0001MV-02 for bug-gnu-emacs@gnu.org; Wed, 22 Dec 2021 11:24:02 -0500 X-Loop: help-debbugs@gnu.org In-Reply-To: <87sfukekpo.fsf@gmx.net> Resent-From: Eric Abrahamsen Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 22 Dec 2021 16:24:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 52735 X-GNU-PR-Package: emacs X-Debbugs-Original-To: bug-gnu-emacs@gnu.org Original-Received: via spool by submit@debbugs.gnu.org id=B.16401902335220 (code B ref -1); Wed, 22 Dec 2021 16:24:01 +0000 Original-Received: (at submit) by debbugs.gnu.org; 22 Dec 2021 16:23:53 +0000 Original-Received: from localhost ([127.0.0.1]:59585 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1n04PB-0001M8-J2 for submit@debbugs.gnu.org; Wed, 22 Dec 2021 11:23:53 -0500 Original-Received: from lists.gnu.org ([209.51.188.17]:45694) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1n04PA-0001M0-Hp for submit@debbugs.gnu.org; Wed, 22 Dec 2021 11:23:52 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:59546) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n04PA-0002Dt-Dc for bug-gnu-emacs@gnu.org; Wed, 22 Dec 2021 11:23:52 -0500 Original-Received: from ciao.gmane.io ([116.202.254.214]:33232) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n04P8-000437-8X for bug-gnu-emacs@gnu.org; Wed, 22 Dec 2021 11:23:51 -0500 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1n04P1-0007Oi-Db for bug-gnu-emacs@gnu.org; Wed, 22 Dec 2021 17:23:43 +0100 X-Injected-Via-Gmane: http://gmane.org/ Received-SPF: pass client-ip=116.202.254.214; envelope-from=geb-bug-gnu-emacs@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: -15 X-Spam_score: -1.6 X-Spam_bar: - X-Spam_report: (-1.6 / 5.0 requ) BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action 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:222951 Archived-At: Stephen Berman writes: > Since more than a week (I think it started on December 11), I've been > regularly experiencing a hang when I type `g' in the Gnus *Group* > buffer: the mouse pointer spins, and Emacs is locked up. Typing `C-g' > releases the hang and then typing `g' again succeeds in fetching new > news. I can also get a hang when typing RET on an article line in the > Gnus *Summary* buffer, and also here typing `C-g' releases the hang and > typing RET again opens the article. These hangs happen reliably when I > don't provide any input to Gnus (e.g., opening a group or an article, or > just check again for new news) within several minutes (I haven't > determined a more precise amount of time). They only involve the > news.gmane.io server, not any of the mail servers I fetch mail from (I > haven't tried any other news server). > > The hang appears to happen in nntp-finish-retrieve-group-infos: stepping > through the code with Edebug, I see an infinite loop here: > > (while (and (gnus-buffer-live-p buf) > (progn > (goto-char last-point) > ;; Count replies. > (while (re-search-forward > (if nntp-server-list-active-group > "^[.]" > "^[0-9]") > nil t) > (cl-incf received)) > (setq last-point (point)) > (< received count))) > (nntp-accept-response)) > > when the server buffer (e.g. " *server news.gmane.io nntp *nntpd**") is > empty. Since this code clearly does not expect an empty buffer, the bug > is presumably making this buffer empty when this code is executed. But > I haven't managed to figure out how this happens. (I have seen that > this buffer can become empty in other situations, e.g. on opening an > article in Gnus, and that doesn't cause any problems.) I've also > observed that when I wait long enough for the server process to close > (the buffer then shows "Process nntpd connection broken by remote > peer"), then there is no hang on typing `g' in the *Group* buffer. The only thing I can suggest now is more debugging on `nntp-finish-retrieve-group-infos', and try to get a backtrace for both the buggy empty-buffer situation, and the normal, non-empty-buffer situation. Perhaps comparing the two backtraces will provide a clue as to how we ended up with an empty buffer?