Acknowledgement sent
to Ludovic Courtès <ludovic.courtes@inria.fr>:
New bug report received and forwarded. Copy sent to bug-guix@gnu.org.
(Thu, 01 Apr 2021 14:01:02 GMT) (full text, mbox, link).
Subject: “Repeated allocation of very large
block” during ‘guix pull’
Date: Thu, 01 Apr 2021 16:00:06 +0200
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’.
Severity set to 'important' from 'normal'
Request was from Ludovic Courtès <ludo@gnu.org>
to control@debbugs.gnu.org.
(Thu, 15 Jun 2023 21:09:02 GMT) (full text, mbox, link).
Information forwarded
to bug-guix@gnu.org: bug#47543; Package guix.
(Wed, 20 Sep 2023 07:25:02 GMT) (full text, mbox, link).
Subject: Re: bug#47543: “Repeated allocation of very
large block” during
‘guix pull’
Date: Sat, 23 Sep 2023 13:40:44 +0200
Janneke Nieuwenhuizen writes:
Hi!
Just a headsup with more information.
> Ludovic Courtès writes:
>
>> If you experience it, please share the command line and command output!
>
> Never seen this before, but here it is...
[..]
> ./guix/store.scm:1036:9: ERROR:
> 1. &store-protocol-error:
> message: "error parsing derivation `/gnu/store/2zb0lb5bkg5868vvwqi6a8nh07p23610-guix-6bd17a080-modules.drv': expected string `Derive(['"
> status: 1
This bit, i.e., the fact that `guix pull' failed, was due to store
corruption. Something else that I've also never experienced before.
> guix pull: error: You found a bug: the program '/gnu/store/sv5bgbzisyii7g45c3bd3w8jk59gfvx0-compute-guix-derivation'
> failed to compute the derivation for Guix (version: "6bd17a0806ad32d1493ac51a7443276f719c4224"; system: "x86_64-linux";
> host version: "445a0359083388b5ee686e6e855f94a3aac5f79c"; pull-version: 1).
> Please report the COMPLETE output above by email to <bug-guix@gnu.org>.
And on that last note, I wonder how apt this massage is, in this
particular case running `guix gc --repair=content' would have been
helpful.
> This seems to be somewhat repeatable, it was the third time in a row
> this failed. After the second time, I removed ~/.cache/guix/checkouts.
After repairing the store, the `large block' warning was also gone.
Greetings,
Janneke
--
Janneke Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond https://LilyPond.org
Freelance IT https://www.JoyOfSource.com | Avatar® https://AvatarAcademy.com
Information forwarded
to bug-guix@gnu.org: bug#47543; Package guix.
(Thu, 23 Nov 2023 11:43:02 GMT) (full text, mbox, link).
Subject: Re: bug#47543: “Repeated allocation of very
large block” during
‘guix pull’
Date: Thu, 23 Nov 2023 12:42:08 +0100
Ludovic Courtès <ludovic.courtes@inria.fr> skribis:
> 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
[...]
> So it might rather be ‘update-cached-checkout’ that triggers it.
I wonder if this was due to the big checkouts we ended up with so far:
https://issues.guix.gnu.org/65720
Ludo’.
Information forwarded
to bug-guix@gnu.org: bug#47543; Package guix.
(Wed, 17 Apr 2024 19:58:01 GMT) (full text, mbox, link).
From: John Kehayias <john.kehayias@protonmail.com>
To: Ludovic Courtès <ludo@gnu.org>
Cc: 47543@debbugs.gnu.org
Subject: Re: bug#47543: “Repeated allocation of very large block” during ‘guix pull’
Date: Wed, 17 Apr 2024 19:56:51 +0000
Hello,
Just hit this warning and went searching to find this report.
On Thu, Nov 23, 2023 at 12:42 PM, Ludovic Courtès wrote:
> Ludovic Courtès <ludovic.courtes@inria.fr> skribis:
>
>> 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
>
> [...]
>
>> So it might rather be ‘update-cached-checkout’ that triggers it.
>
> I wonder if this was due to the big checkouts we ended up with so far:
>
> https://issues.guix.gnu.org/65720
>
> Ludo’.
In my case, just did a guix pull so I am on
2126dab4cd81db4cbde4566d8c638e45a4c0077c.
Pull was fine, but this warning was repeatable on a system reconfigure:
--8<---------------cut here---------------start------------->8---
❯ sudo guix system reconfigure ~/.config/guix/config.scm --max-jobs=4 -n
GC Warning: Repeated allocation of very large block (appr. size 69632):
May lead to memory leak and poor performance
GC Warning: Repeated allocation of very large block (appr. size 69632):
May lead to memory leak and poor performance
GC Warning: Repeated allocation of very large block (appr. size 69632):
May lead to memory leak and poor performance
GC Warning: Repeated allocation of very large block (appr. size 135168):
May lead to memory leak and poor performance
GC Warning: Repeated allocation of very large block (appr. size 131072):
May lead to memory leak and poor performance
GC Warning: Repeated allocation of very large block (appr. size 69632):
May lead to memory leak and poor performance
GC Warning: Repeated allocation of very large block (appr. size 102400):
May lead to memory leak and poor performance
substitute: updating substitutes from 'https://bordeaux-us-east-mirror.cbaines.net/'... 100.0%
substitute: updating substitutes from 'https://bordeaux.guix.gnu.org'... 100.0%
substitute: updating substitutes from 'https://ci.guix.gnu.org'... 100.0%
substitute: updating substitutes from 'https://substitutes.nonguix.org'... 100.0%
The following derivation would be built:
/gnu/store/r9n8vz4s1n7v3551cphrqy0pqyl8wcv0-corectrl-1.3.5.drv
340.3 MB would be downloaded
❯ sudo guix system reconfigure ~/.config/guix/config.scm -n
GC Warning: Repeated allocation of very large block (appr. size 69632):
May lead to memory leak and poor performance
GC Warning: Repeated allocation of very large block (appr. size 122880):
May lead to memory leak and poor performance
GC Warning: Repeated allocation of very large block (appr. size 69632):
May lead to memory leak and poor performance
GC Warning: Repeated allocation of very large block (appr. size 69632):
May lead to memory leak and poor performance
GC Warning: Repeated allocation of very large block (appr. size 69632):
May lead to memory leak and poor performance
The following derivation would be built:
/gnu/store/r9n8vz4s1n7v3551cphrqy0pqyl8wcv0-corectrl-1.3.5.drv
340.3 MB would be downloaded
❯ sudo guix system reconfigure ~/.config/guix/config.scm --max-jobs=4
GC Warning: Repeated allocation of very large block (appr. size 69632):
May lead to memory leak and poor performance
GC Warning: Repeated allocation of very large block (appr. size 69632):
May lead to memory leak and poor performance
GC Warning: Repeated allocation of very large block (appr. size 69632):
May lead to memory leak and poor performance
GC Warning: Repeated allocation of very large block (appr. size 131072):
May lead to memory leak and poor performance
The following derivation will be built:
/gnu/store/r9n8vz4s1n7v3551cphrqy0pqyl8wcv0-corectrl-1.3.5.drv
340.3 MB will be downloaded
adwaita-icon-theme-44.0 904KiB 108.0MiB/s 00:00 ▕██████████████████▏ 100.0%
guix substitute: warning: download from 'https://bordeaux-us-east-mirror.cbaines.net/nar/lzip/c2brbsvn75866l81rswb7z8sdpw2dvjr-font-abattis-cantarell-0.303-0.e049149' failed: 404, "Not Found"
retrying download of '/gnu/store/c2brbsvn75866l81rswb7z8sdpw2dvjr-font-abattis-cantarell-0.303-0.e049149' with other substitute URLs...
substitution of
/gnu/store/5in68ily7wjj8jy67kyj8sikwmci894j-ath9k-htc-ar7010-firmware-1.4.0
complete
--8<---------------cut here---------------end--------------->8---
this last one continued until I killed it to send capture the previous
output and send it.
--8<---------------cut here---------------start------------->8---
❯ free -h
total used free shared buff/cache available
Mem: 15Gi 10Gi 3.4Gi 706Mi 2.4Gi 4.8Gi
Swap: 15Gi 4.1Gi 11Gi
--8<---------------cut here---------------end--------------->8---
But since interrupting the reconfigure, it doesn't give the warning
again. So something happened by actually starting the reconfigure
process...?
I don't think I've ever seen this before. Hope this helps!
John
Debbugs is free software and licensed under the terms of the
GNU Public License version 2. The current version can be
obtained from https://bugs.debian.org/debbugs-source/.