unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: 33018@debbugs.gnu.org
Subject: bug#33018: 26.1.50; thread starvation with async processes and accept-process-output
Date: Fri, 12 Oct 2018 11:07:21 +0300	[thread overview]
Message-ID: <83o9bzwpty.fsf@gnu.org> (raw)
In-Reply-To: <87r2gwbmma.fsf@tcd.ie> (contovob@tcd.ie)

> From: "Basil L. Contovounesios" <contovob@tcd.ie>
> Date: Thu, 11 Oct 2018 15:57:50 +0100
> 
> I attach a sample program test.el whose central function, test-slave,
> invokes wget asynchronously before waiting for the process to exit.
> 
> The issue I'm facing is that running test-slave twice in succession,
> each time in a new thread, causes accept-process-output to hang with no
> output (unless a timeout argument is given, in which case the function
> returns nil) the second time around.

When the hang happens, is there any wget process still alive, or did
they all exit?  Please use OS tools to find that out, don't rely on
what Emacs thinks.

> I could very well be doing or assuming something incorrectly, but what
> baffles me is that the "hang" does not occur either when Emacs is run
> non-interactively, or when "https://en.wikipedia.org/wiki/Emacs" is
> replaced with "https://www.gnu.org/software/emacs/"

Could be different properties of the servers related to async
connections, like TLS handshake or even async getaddrinfo.





  reply	other threads:[~2018-10-12  8:07 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-11 14:57 bug#33018: 26.1.50; thread starvation with async processes and accept-process-output Basil L. Contovounesios
2018-10-12  8:07 ` Eli Zaretskii [this message]
2018-10-14 15:00   ` Basil L. Contovounesios
2018-10-14 15:17     ` Eli Zaretskii
2018-10-14 15:36       ` Basil L. Contovounesios
2018-10-12 12:02 ` Michael Albinus
2018-10-12 12:43   ` Eli Zaretskii
2018-10-12 12:49     ` Michael Albinus
2018-10-14 15:17   ` Basil L. Contovounesios
2018-10-15  8:02     ` Michael Albinus
2018-10-16  1:15       ` Basil L. Contovounesios
2018-10-16 13:54         ` Michael Albinus
2018-10-16 14:55           ` Basil L. Contovounesios
2018-10-16 14:58         ` Eli Zaretskii
2018-10-17 17:37           ` Basil L. Contovounesios
2018-10-17 17:56             ` Eli Zaretskii
2018-10-17 18:05               ` Basil L. Contovounesios
2018-10-17 18:20                 ` Eli Zaretskii
2018-10-17 18:25                   ` Eli Zaretskii
2018-10-17 20:46                     ` Basil L. Contovounesios
2018-10-20  8:34                       ` Eli Zaretskii
2018-10-17 20:02                   ` Basil L. Contovounesios

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83o9bzwpty.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=33018@debbugs.gnu.org \
    --cc=contovob@tcd.ie \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).