From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: "Basil L. Contovounesios" Newsgroups: gmane.emacs.bugs Subject: bug#24201: 25.1.50; TLS connections sometimes hang Date: Fri, 28 Jun 2019 15:39:04 +0100 Message-ID: <87ftntkc53.fsf@tcd.ie> References: <83d1j8e9c0.fsf@gnu.org> <83shg5z32d.fsf@gnu.org> <87efrp2qw0.fsf@mouse> <83tw0lxjt3.fsf@gnu.org> <6e9f3b6c-43df-bf95-d346-56c93c61b4d7@cs.ucla.edu> <83o9kk96ez.fsf@gnu.org> <83h8qc92hc.fsf@gnu.org> <834l4en63b.fsf@gnu.org> <83h88cjoiv.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="176464"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) Cc: eggert@cs.ucla.edu, 24201@debbugs.gnu.org To: Lars Ingebrigtsen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Fri Jun 28 17:09:30 2019 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([209.51.188.17]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1hgsVB-000jii-Rg for geb-bug-gnu-emacs@m.gmane.org; Fri, 28 Jun 2019 17:09:26 +0200 Original-Received: from localhost ([::1]:33034 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hgsVA-00064K-Os for geb-bug-gnu-emacs@m.gmane.org; Fri, 28 Jun 2019 11:09:24 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:44176) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hgs2l-0004FM-UJ for bug-gnu-emacs@gnu.org; Fri, 28 Jun 2019 10:40:04 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hgs2k-0006oJ-Vj for bug-gnu-emacs@gnu.org; Fri, 28 Jun 2019 10:40:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:57440) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hgs2k-0006nz-SK for bug-gnu-emacs@gnu.org; Fri, 28 Jun 2019 10:40:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hgs2k-0005FP-KC for bug-gnu-emacs@gnu.org; Fri, 28 Jun 2019 10:40:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: "Basil L. Contovounesios" Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 28 Jun 2019 14:40:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 24201 X-GNU-PR-Package: emacs Original-Received: via spool by 24201-submit@debbugs.gnu.org id=B24201.156173275420081 (code B ref 24201); Fri, 28 Jun 2019 14:40:02 +0000 Original-Received: (at 24201) by debbugs.gnu.org; 28 Jun 2019 14:39:14 +0000 Original-Received: from localhost ([127.0.0.1]:42751 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1hgs1y-0005Dn-92 for submit@debbugs.gnu.org; Fri, 28 Jun 2019 10:39:14 -0400 Original-Received: from mail-ed1-f65.google.com ([209.85.208.65]:38947) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1hgs1w-0005DZ-8q for 24201@debbugs.gnu.org; Fri, 28 Jun 2019 10:39:12 -0400 Original-Received: by mail-ed1-f65.google.com with SMTP id m10so11120491edv.6 for <24201@debbugs.gnu.org>; Fri, 28 Jun 2019 07:39:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tcd-ie.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version; bh=wEYSRl8XHqKYJrn2CnUs1f2cI5WHs5+WaHTNkOR8mGI=; b=e/nY4Cn7EeJ9Kfk58+ibCTqyg88nAwYgy7X0f4lb3rGUkB/DLu5zPugrsTMS2x9lye kRoaTGcR3xGmkufpdadYIrVAcnVz8YAQqzQwUVUSGhKASp6QXSFGTRQMaybYSM4aJfpM Fqc2ai07iihIGlrB4+rjHlO3p7ihQO2IHLjlOyKYrVrPcHQkagJghCm1ul7KSPSLHe+R vJVDCyaoDwu+ccUnS3tWbiMmxWTEi2ZStvfYs0cHqbL725dyhoa6fH/DHaVhyqB9trkF yyt000sr+u/vmuMa79ZwVKNThSO17riFVvtpoloGTjTykrdc6oKxBo7NS3t/qTYzqPRu W2fg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version; bh=wEYSRl8XHqKYJrn2CnUs1f2cI5WHs5+WaHTNkOR8mGI=; b=Mv/SZN90ZXlqONkKWmWc3eM9gktmJz1uAQ6Tia0aaQ0zNe7kwc7g5mBn2dBIg8VkT4 MRROZcDWNDba3SRTFDvV7reudgqzFr+SvityfvIbmqVfu5ZoiZ8vsiOVtvxEmP+4QnfO iwmq+Sjmb7LG4awYW5Vfm3ATLA5Q9W+uZLiGnMDMDEUWMjgboWjFz+FnYUTlkf9YbRGV jPjmPyTrZnuU/vL/PsYBhOGflZJeZnVd67owY8/K2VA713Gc5M+IbfW7WmxiMD6gKo86 bb35AuaHrGUIMhGcy0UBPqfPr9fg+j1dXCSUXpKrgeu5blhyz3k92+eNb83W+SDBW2S1 ewhw== X-Gm-Message-State: APjAAAV5rY/6/UQ0kP24CPZz+/2Vq8wu5+D1O/zDxFgQyrMmoBrSbra9 jNsOD+ovFe7rHQXvN9jr6V+Hzg== X-Google-Smtp-Source: APXvYqw6XXKdI9cMTgBKG+kEgouqUksX+jNgJttjAoQO1iicUlB+EqGv9m10l5pVzkNikOnLjTJnWw== X-Received: by 2002:a17:906:6b53:: with SMTP id o19mr9120611ejs.27.1561732746358; Fri, 28 Jun 2019 07:39:06 -0700 (PDT) Original-Received: from localhost ([2a02:8084:20e2:c380:92bd:1bfd:38fc:fae2]) by smtp.gmail.com with ESMTPSA id l38sm749612eda.1.2019.06.28.07.39.05 (version=TLS1_3 cipher=AEAD-AES256-GCM-SHA384 bits=256/256); Fri, 28 Jun 2019 07:39:05 -0700 (PDT) In-Reply-To: (Lars Ingebrigtsen's message of "Thu, 27 Jun 2019 12:34:28 +0200") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 209.51.188.43 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.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:161729 Archived-At: Lars Ingebrigtsen writes: > Eli Zaretskii writes: > >> OK, so that Ffuncall calls network-stream-get-response. the next >> question is what Lisp code runs 2 stack frames above, i.e. which Lisp >> code calls some other Lisp code, which calls >> network-stream-get-response? Can you spot that? The offending code >> should be somewhere in network-stream-get-response or functions it >> calls. >> >> Once we identify the Lisp code which loops, we need to try to figure >> out why it loops. > > I'm pretty sure it's this: > > (while (and (memq (process-status stream) '(open run)) > (not (re-search-forward end-of-command nil t))) > (accept-process-output stream 0.05) > (goto-char start)) This is probably unrelated, but isn't there a race condition between checking process-status and accepting output, as described in (info "(elisp) Accepting Output")? Thanks, -- Basil