From: "Ludovic Courtès" <ludo@gnu.org>
To: Caleb Ristvedt <caleb.ristvedt@cune.org>
Cc: 41204-done@debbugs.gnu.org
Subject: bug#41204: port-revealed count is initially > 30000
Date: Tue, 12 May 2020 15:04:16 +0200 [thread overview]
Message-ID: <87ftc5b8z3.fsf@gnu.org> (raw)
In-Reply-To: <878shxqw9k.fsf@cune.org> (Caleb Ristvedt's message of "Tue, 12 May 2020 05:32:07 -0500")
Hi,
Caleb Ristvedt <caleb.ristvedt@cune.org> skribis:
> (port-revealed (open-input-file "/dev/null"))
> => 32539
Fixed in b1bdd791cefa1b6d113f9b3972550342d8f4aa9f.
Guile up to 2.2.7/3.0.2 included (but not 2.0) would thus leak the file
descriptors of all the file ports not explicitly closed. It’s probably
not that common (good practice is too close file ports as soon as you’re
done with them and ‘call-with-output-file’ & co. take care of that), but
still.
Thanks a lot for finding the problem!
Ludo’.
prev parent reply other threads:[~2020-05-12 13:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 10:32 bug#41204: port-revealed count is initially > 30000 Caleb Ristvedt
2020-05-12 13:04 ` Ludovic Courtès [this message]
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/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ftc5b8z3.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=41204-done@debbugs.gnu.org \
--cc=caleb.ristvedt@cune.org \
/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.
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).