tags 1024532 - moreinfo
close 1024532 1.79.3-1
thanks
I can verify that the version currently in trixie does not show this
behaviour anymore (maximum allocated memory is now below 1 GB).
Therefore I'm closing this bug myself.
(It would have been interesting maybe to know in which version it
was
El 22/11/22 a las 0:40, Jeremy Bicha escribió:
On Mon, Nov 21, 2022 at 7:54 AM Santiago Vila wrote:
Not exactly. As explained, I am intentionally measuring the allocated
memory as a completely safe upper bound for the required memory, and I
am aware that they are not the same. Nevertheless, I t
Oh, yes... So I agree that seems to be a problem.
We should probably try to run the tests alone to figure out which ones
are causing the issue.
Hi.
I confirm that the huge memory allocation happens during the
override_dh_auto_test target of debian/rules, not during the build itself.
This is at least double the amount of *any other* of the 33785 source
packages in Debian bookworm, so yes, I think it is more than fair to
call it an an
El 22/11/22 a las 18:44, Marco Trevisan escribió:
On nov 21 2022, at 1:51 pm, Santiago Vila wrote:
I am reporting this as an anomaly (a very big anomaly indeed).
With the gjs upstream hat, I have sadly to say that this is probably
something expected: gjs eavily uses complex templates to gener
Hi,
On nov 21 2022, at 1:51 pm, Santiago Vila wrote:
> El 21/11/22 a las 11:20, Simon McVittie escribió:
>> In case there's a kernel difference, I've just tried it in a bookworm
>> VM containing bookworm's sbuild and schroot, again with 2G of RAM. That
>> was also successful.
>
> The package b
On Mon, Nov 21, 2022 at 7:54 AM Santiago Vila wrote:
> El 21/11/22 a las 11:20, Simon McVittie escribió:
> > I think you might accidentally be measuring how much it *can* allocate
> > if given the opportunity, as opposed to how much it strictly *needs*
> > to allocate?
>
> Not exactly. As explaine
El 21/11/22 a las 11:20, Simon McVittie escribió:
When I upload it, I do my test-build in a VM with 2G of RAM, and that
works fine. I'm using a bullseye VM containing bullseye's sbuild and
schroot, with gjs built in a sid chroot by that copy of sbuild. This
is intended to replicate Debian's produ
Control: tags -1 + moreinfo
On Mon, 21 Nov 2022 at 01:59:09 +0100, Santiago Vila wrote:
> During a mass rebuild of all packages in bookworm, I noticed that gjs
> allocates up to 237 GB of memory.
When I upload it, I do my test-build in a VM with 2G of RAM, and that
works fine. I'm using a bullsey
Package: src:gjs
Version: 1.74.1-1
X-Debbugs-Cc: sanv...@debian.org
Dear maintainer:
During a mass rebuild of all packages in bookworm, I noticed that gjs
allocates up to 237 GB of memory.
I measure this by monitoring Committed_AS parameter in /proc/meminfo at
every second during the build.
10 matches
Mail list logo
