unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: 47543@debbugs.gnu.org
Subject: bug#47543: “Repeated allocation of very large block” during ‘guix pull’
Date: Thu, 01 Apr 2021 16:00:06 +0200	[thread overview]
Message-ID: <87v9966r6h.fsf@inria.fr> (raw)

While running ‘guix pull’, sometime between the actual ‘git pull’ (via
Guile-Git) and channel authentication, I saw the dreaded libgc warning:

  Repeated allocation of very large block

I forgot to capture the command output though, and it does not seem to
be reproducible.  (This is with a recent Guix,
ca. 9098745b181b3022587a35afd255f7ff1d41ac86.)

Running the command below from a Guix checkout, which authenticates 15+K
commits, isn’t enough to trigger it:

  guix git authenticate --cache-key=whatever \
    "9edb3f66fd807b096b48283debdcddccfea34bad" \
    "BBB0 2DDF 2CEA F6A8 0D1D E643 A2A0 6DF2 A33A 54FA"

So it might rather be ‘update-cached-checkout’ that triggers it.

If you experience it, please share the command line and command output!

Ludo’.




             reply	other threads:[~2021-04-01 14:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-01 14:00 Ludovic Courtès [this message]
2023-09-20  7:23 ` bug#47543: "Repeated allocation of very large block" during `guix pull` Rostislav Svoboda
2023-09-20  8:02   ` Rostislav Svoboda
2023-09-22 17:25 ` bug#47543: “Repeated allocation of very large block” during ‘guix pull’ Janneke Nieuwenhuizen
2023-09-23 11:40   ` Janneke Nieuwenhuizen
2023-11-23 11:42 ` 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=87v9966r6h.fsf@inria.fr \
    --to=ludovic.courtes@inria.fr \
    --cc=47543@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 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).