Your message dated Sat, 11 May 2024 19:07:44 +0200
with message-id <[email protected]>
and subject line Re: [pkg-gnupg-maint] Bug#852106: gpgme1.0: Build allocates
200 GB as a normal thing
has caused the Debian Bug report #852106,
regarding gpgme1.0: Build allocates 200 GB as a normal thing
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
852106: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852106
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: gpgme1.0
Version: 1.8.0-3
Hello dkg et al.
I have a cron job monitoring "Committed_AS" in /proc/meminfo every time
my autobuilders are running, that way I know how much memory each
package requires.
Well, building gpgme1.0 allocates 100 GB, 200 GB and sometimes 500 GB.
To see how this could be a problem, take a machine with a lot of
memory, say, 64 GB of RAM, which btw is more than three times the
amount required to build any other Debian package, and disable memory
overcommiting by creating /etc/sysctl.d/10-no-overcommit.conf with
this contents:
vm.overcommit_ratio = 100
vm.overcommit_memory = 2
Then write "sysctl --system" to load those values.
Then try to build this package in such machine, and it will fail.
I have detected only one other package with a problem like this.
If you are curious:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848589
Every other package which I tried builds fine with only 20 GB of RAM,
so this is clearly an anomaly.
Thanks.
--- End Message ---
--- Begin Message ---
Version: 1.14.0-1
This does not seem to happen anymore. I'm closing with bullseye version,
because that's as far as I currently keep memory usage statistics.
[ The exact version where this was probably fixed is left as a pastime
to bug archeologists, if any ].
Thanks.
--- End Message ---
