From: Joshua Branson via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 58631@debbugs.gnu.org
Subject: bug#58631: [Shepherd] Indefinite heap growth (memory leak)
Date: Thu, 20 Oct 2022 13:49:38 -0400 [thread overview]
Message-ID: <878rlajsgd.fsf_-_@dismail.de> (raw)
In-Reply-To: <87sfjjhjcd.fsf@gnu.org> ("Ludovic Courtès"'s message of "Wed, 19 Oct 2022 18:24:50 +0200")
Ludovic Courtès <ludo@gnu.org> writes:
> Indeed, the core dump weighs 13 GiB, so it looks like a memory leak (too
> bad ‘info proc stat’ in GDB doesn’t work).
>
> I have not observed it on any other machine. The difference between
> berlin and machines I have access to is that berlin is being hammered on
> port 22, which means it gets to spawn sshd processes very often. This
> could be where the leak is.
>
So, this is a hack, but perhaps berlin could start to use endlessh on
port 22, and then the real ssh port could be on another standard port.
https://issues.guix.gnu.org/39136
It would change most guix developers work loads. But it's a thought. :)
> Ludo’.
next prev parent reply other threads:[~2022-10-20 17:50 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
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 [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878rlajsgd.fsf_-_@dismail.de \
--to=bug-guix@gnu.org \
--cc=58631@debbugs.gnu.org \
--cc=jbranso@dismail.de \
--cc=ludo@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 public inbox
https://git.savannah.gnu.org/cgit/guix.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).