From: Eli Zaretskii <eliz@gnu.org>
To: Andrea Corallo <akrl@sdf.org>
Cc: stepheng+emacs@gildea.com, 51110@debbugs.gnu.org
Subject: bug#51110: Native-comp leaks fds open on /dev/ptmx
Date: Tue, 30 Nov 2021 22:18:51 +0200 [thread overview]
Message-ID: <83a6hltn10.fsf@gnu.org> (raw)
In-Reply-To: <xjftuftz9kc.fsf@ma.sdf.org> (message from Andrea Corallo on Tue, 30 Nov 2021 20:13:07 +0000)
> From: Andrea Corallo <akrl@sdf.org>
> Cc: Stephen Gildea <stepheng+emacs@gildea.com>, 51110@debbugs.gnu.org
> Date: Tue, 30 Nov 2021 20:13:07 +0000
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: Stephen Gildea <stepheng+emacs@gildea.com>
> >> cc: Andrea Corallo <akrl@sdf.org>, 51110@debbugs.gnu.org
> >> Date: Sat, 09 Oct 2021 10:01:43 -0700
> >>
> >> Apparently what's happening is that Emacs forks off a child Emacs to do
> >> the compile and allocates a pty to the child. These ptys are not
> >> closed until the compile completes. It seems Emacs needs to better
> >> manage the number of simultaneous open ptys. Or at least be able to
> >> wait and retry if an open fails.
> >
> > Emacs limits the number of these background processes, see
> > native-comp-async-jobs-number. (The value zero means use half of the
> > number of execution units available in the system's processor.) So we
> > generally shouldn't have more than that number of open pipes at any
> > given time. For the obvious reasons they cannot be closed until the
> > sub-process exits.
>
> Is there any action we need/can take on this bug?
I don't think there's anything we _can_ do here, and I tried to
explain why.
next prev parent reply other threads:[~2021-11-30 20:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-09 15:45 bug#51110: Native-comp leaks fds open on /dev/ptmx Stephen Gildea
2021-10-09 15:57 ` Eli Zaretskii
2021-10-09 17:01 ` Stephen Gildea
2021-10-09 17:15 ` Eli Zaretskii
2021-11-30 20:13 ` Andrea Corallo
2021-11-30 20:18 ` Eli Zaretskii [this message]
2021-11-30 20:24 ` Andrea Corallo
2021-11-30 20:29 ` Eli Zaretskii
2021-12-01 2:28 ` Stephen Gildea
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=83a6hltn10.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=51110@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=stepheng+emacs@gildea.com \
/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).