From: Eli Zaretskii <eliz@gnu.org>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: michael.albinus@gmx.de, 33018@debbugs.gnu.org
Subject: bug#33018: 26.1.50; thread starvation with async processes and accept-process-output
Date: Sat, 20 Oct 2018 11:34:40 +0300 [thread overview]
Message-ID: <83efcluicf.fsf@gnu.org> (raw)
In-Reply-To: <87zhvc2te8.fsf@tcd.ie> (contovob@tcd.ie)
> From: "Basil L. Contovounesios" <contovob@tcd.ie>
> Cc: <michael.albinus@gmx.de>, <33018@debbugs.gnu.org>
> Date: Wed, 17 Oct 2018 21:46:39 +0100
>
> > I think the relevant code should be instrumented to show which thread
> > waits for what process(es).
>
> Each thread launches a single wget process which it then waits for
> before dying, and current-thread is always eq to that thread around
> calls to accept-process-output. Or are you talking about some other
> type of thread?
I was talking about low-level details: we set up the file-descriptor
mask passed to pselect, to tell it which descriptors to wait on. The
call to accept-process-output is supposed to arrange for the
descriptor where the corresponding process will write to be one of
those on which the corresponding pselect will wait. I was thinking
that perhaps we become confused and don't ask pselect called by a
thread to wait on the process which was launched by that thread.
> Either way, I'll report back when I've had a deeper look into what Emacs
> is doing, unless someone beats me to it.
Thanks.
> I'm sorry I've been talking more than doing, but university and house
> hunting will dominate my free time for the next few weeks.
No need to be sorry, we all have our lives.
next prev parent reply other threads:[~2018-10-20 8:34 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83efcluicf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=33018@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=michael.albinus@gmx.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.