GNU bug report logs - #46624
Too many heap sections: Increase MAXHINCR or MAX_HEAP_SEC

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 46624 in the body.
You can then email your comments to 46624 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Sharlatan Hellseher <sharlatanus <at> gmail.com>
To: bug-guix <at> gnu.org
Subject: Too many heap sections: Increase MAXHINCR or MAX_HEAP_SEC
Date: Thu, 18 Feb 2021 20:42:50 +0000

./pre-inst-env guix build sbcl-cffi ;;; note: source file
/home/hellseher/code/guix/gnu/packages/lisp-xyz.scm ;;; newer than
compiled /home/hellseher/code/guix/gnu/packages/lisp-xyz.go Too many
heap sections: Increase MAXHINCR or MAX_HEAP_SECS
Aborted

-- 
… наш разум - превосходная объяснительная машина которая способна
найти смысл почти в чем угодно, истолковать любой феномен, но
совершенно не в состоянии принять мысль о непредсказуемости.

Message #8 received at 46624 <at> debbugs.gnu.org (full text, mbox):

From: Guillaume Le Vaillant <glv <at> posteo.net>
To: Sharlatan Hellseher <sharlatanus <at> gmail.com>
Cc: 46624 <at> debbugs.gnu.org
Subject: Re: bug#46624: Too many heap sections: Increase MAXHINCR or
 MAX_HEAP_SEC
Date: Thu, 18 Feb 2021 22:05:43 +0100

[Message part 1 (text/plain, inline)]

Sharlatan Hellseher <sharlatanus <at> gmail.com> skribis:

> ./pre-inst-env guix build sbcl-cffi ;;; note: source file
> /home/hellseher/code/guix/gnu/packages/lisp-xyz.scm ;;; newer than
> compiled /home/hellseher/code/guix/gnu/packages/lisp-xyz.go Too many
> heap sections: Increase MAXHINCR or MAX_HEAP_SECS
> Aborted

With Guix at 5fccdbc079402eee345684bcbd1b1d0306cab1e8 I don't reproduce
this issue.
From the warning and error messages you get, it looks like you changed
something in 'lisp-xyz.scm' and Guix fails to compile it.
Is it the case? If yes, there is probably a bug in the changes you made.

[signature.asc (application/pgp-signature, inline)]

Message #11 received at 46624 <at> debbugs.gnu.org (full text, mbox):

From: Tobias Geerinckx-Rice <me <at> tobias.gr>
To: Guillaume Le Vaillant <glv <at> posteo.net>
Cc: bug-guix <at> gnu.org, Sharlatan Hellseher <sharlatanus <at> gmail.com>,
 46624 <at> debbugs.gnu.org
Subject: Re: bug#46624: Too many heap sections: Increase MAXHINCR or
 MAX_HEAP_SEC
Date: Thu, 18 Feb 2021 23:02:06 +0100

[Message part 1 (text/plain, inline)]

Guillaume Le Vaillant 写道：
> From the warning and error messages you get, it looks like you 
> changed
> something in 'lisp-xyz.scm' and Guix fails to compile it.
> Is it the case? If yes, there is probably a bug in the changes 
> you made.

More specifically, it's likely an input cycle (infinite loop of A 
needs B needs ... needs A).  Guix doesn't [yet] detect these, and 
takes them literally until memory is exhausted.

Kind regards,

T G-R

[signature.asc (application/pgp-signature, inline)]

Message #19 received at 46624-done <at> debbugs.gnu.org (full text, mbox):

From: Guillaume Le Vaillant <glv <at> posteo.net>
To: Sharlatan Hellseher <sharlatanus <at> gmail.com>
Cc: 46624-done <at> debbugs.gnu.org
Subject: Re: bug#46624: Too many heap sections: Increase MAXHINCR or
 MAX_HEAP_SEC
Date: Fri, 19 Feb 2021 09:19:43 +0100

[Message part 1 (text/plain, inline)]

Sharlatan Hellseher <sharlatanus <at> gmail.com> skribis:

> Hi,
>
> Yes it looks like issue on my end only.
> I've doped my local branch pull upstream and I could rebuild it now.
> Issue could be closed.
>
> Thanks
>
> hellseher <at> guix-base-20210210 ~/code/guix [env]$ ./pre-inst-env guix
> build sbcl-cffi
> ;;; note: source file /home/hellseher/code/guix/gnu/packages/lisp-xyz.scm
> ;;;       newer than compiled /home/hellseher/code/guix/gnu/packages/lisp-xyz.go
> ;;; note: source file /home/hellseher/code/guix/gnu/packages/emacs-xyz.scm
> ;;;       newer than compiled
> /home/hellseher/code/guix/gnu/packages/emacs-xyz.go
> ;;; note: source file /home/hellseher/code/guix/gnu/packages/games.scm
> ;;;       newer than compiled /home/hellseher/code/guix/gnu/packages/games.go
> ;;; note: source file /home/hellseher/code/guix/gnu/packages/telegram.scm
> ;;;       newer than compiled /home/hellseher/code/guix/gnu/packages/telegram.go
> /gnu/store/x9ainb8phlprackcdwl1a8w0xh1bh18g-sbcl-cffi-0.23.0

Ok, closing.

[signature.asc (application/pgp-signature, inline)]

Message #22 received at 46624 <at> debbugs.gnu.org (full text, mbox):

From: zimoun <zimon.toutoune <at> gmail.com>
To: Tobias Geerinckx-Rice <me <at> tobias.gr>, Guillaume Le Vaillant
 <glv <at> posteo.net>
Cc: sharlatanus <at> gmail.com, 46624 <at> debbugs.gnu.org
Subject: Re: bug#46624: Too many heap sections: Increase MAXHINCR or
 MAX_HEAP_SEC
Date: Wed, 24 Feb 2021 23:41:17 +0100

Hi Tobias,

On Thu, 18 Feb 2021 at 23:02, Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix <at> gnu.org> wrote:

> More specifically, it's likely an input cycle (infinite loop of A 
> needs B needs ... needs A).  Guix doesn't [yet] detect these, and 
> takes them literally until memory is exhausted.

Where should this feature go?  Under “guix lint” via another checker or
“guix build” walking the graph to detect cycles before really building?


Cheers,
simon

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.