From: "Ludovic Courtès" <ludo@gnu.org>
To: 58631@debbugs.gnu.org
Subject: bug#58631: [Shepherd] Indefinite heap growth (memory leak)
Date: Sun, 06 Nov 2022 23:45:06 +0100 [thread overview]
Message-ID: <87edufg0st.fsf@gnu.org> (raw)
In-Reply-To: <87mt9dzm3q.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sun, 30 Oct 2022 10:39:37 +0100")
Ludovic Courtès <ludo@gnu.org> skribis:
> Ludovic Courtès <ludo@gnu.org> skribis:
>
>> The attached Fibers program illustrates the problem: heap grows even
>> though it’s not supposed to.
>
> The saga continues at <https://github.com/wingo/fibers/issues/65>.
… and then at <https://issues.guix.gnu.org/59021>, which appears to have
a happy end: these Guix commits deploy the fix:
072fd1124a gnu: shepherd@0.9: Use 'guile-3.0-latest' to address memory leak.
7138ba34fa gnu: guile@3.0.8: Add patch to address continuation memory leak.
In my testing it fixes the problem. It’s now deployed it on
bayfront.guix.gnu.org and we’ll deploy to berlin.guix.gnu.org later on
and see how it goes in the coming days.
Ludo’.
next prev parent reply other threads:[~2022-11-06 22:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-19 12:17 bug#58631: Shepherd crash on berlin Ludovic Courtès
2022-10-19 16:24 ` Ludovic Courtès
2022-10-20 9:29 ` Ludovic Courtès
2022-10-21 13:07 ` Liliana Marie Prikler
2022-10-22 20:20 ` bug#58631: [Shepherd] Indefinite heap growth (memory leak) Ludovic Courtès
2022-10-22 20:21 ` Ludovic Courtès
2022-10-22 20:29 ` Ludovic Courtès
2022-10-29 10:01 ` Ludovic Courtès
2022-10-29 14:54 ` Maxime Devos
2022-10-30 9:39 ` Ludovic Courtès
2022-11-06 22:45 ` Ludovic Courtès [this message]
2022-11-07 10:43 ` Ludovic Courtès
2022-11-10 8:51 ` Ludovic Courtès
2022-11-11 10:55 ` Ludovic Courtès
2022-10-20 17:49 ` Joshua Branson via Bug reports for GNU Guix
2022-10-20 21:46 ` Ludovic Courtès
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=87edufg0st.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=58631@debbugs.gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.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.