GNU bug report logs - #62623
(backtrace) hangs and causes excessive memory usage

Previous Next

Package: guile;

Reported by: Christopher Baines <mail <at> cbaines.net>

Date: Sun, 2 Apr 2023 17:57:02 UTC

Severity: normal

To reply to this bug, email your comments to 62623 AT debbugs.gnu.org.

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

View this report as an mbox folder, status mbox, maintainer mbox


Report forwarded to bug-guile <at> gnu.org:
bug#62623; Package guile. (Sun, 02 Apr 2023 17:57:02 GMT) Full text and rfc822 format available.

Acknowledgement sent to Christopher Baines <mail <at> cbaines.net>:
New bug report received and forwarded. Copy sent to bug-guile <at> gnu.org. (Sun, 02 Apr 2023 17:57:02 GMT) Full text and rfc822 format available.

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

From: Christopher Baines <mail <at> cbaines.net>
To: bug-guile <at> gnu.org
Subject: (backtrace) hangs and causes excessive memory usage
Date: Sun, 02 Apr 2023 18:38:26 +0100
I've got this problem in the guix-build-coordinator, but I've been so
far unable to reproduce it in a standalone manor.

When (backtrace) is called, the output seems to start, but then stops as
seen below. The memory usage also seems to then start increasing with
increasingly large jumps over a period of hours.

I've seen calling (backtrace) crash before, but this behaviour where it
seems to get stuck is new. I can't tell for sure whether the excessive
memory usage is directly related, or a consequence of the problem.

I've included some output from (backtrace) where this problem occurs
below.


Backtrace:
In ice-9/boot-9.scm:
  1752:10 13 (with-exception-handler _ _ #:unwind? _ # _)
In guix-build-coordinator/coordinator.scm:
    900:9 12 (_)
In prometheus.scm:
    429:4 11 (call-with-duration-metric _ _ _ #:buckets _ #:docstring …)
In ice-9/boot-9.scm:
  1747:15 10 (with-exception-handler #<procedure 7f18a15931c0 at gu…> …)
In guix-build-coordinator/coordinator.scm:
   913:15  9 (_)
In ice-9/boot-9.scm:
  1752:10  8 (with-exception-handler _ _ #:unwind? _ # _)
In guix-build-coordinator/coordinator.scm:
   915:19  7 (_)
   858:10  6 


Backtrace:
In guix-build-coordinator/utils.scm:
   1179:6 13 (_)
In ice-9/boot-9.scm:
  1747:15 12 (with-exception-handler #<program 7fb7adc56a00 7fb7ab4…> …)
  1747:15 11 (with-exception-handler #<program 7fb7adbf6f00 7fb7a98…> …)
In guix-build-coordinator/coordinator.scm:
   1011:8 10 (_)
In ice-9/boot-9.scm:
  1752:10  9 (with-exception-handler _ _ #:unwind? _ # _)
In prometheus.scm:
    429:4  8 (call-with-duration-metric _ _ _ #:buckets _ #:docstring …)
In ice-9/eval.scm:
    619:8  7




Information forwarded to bug-guile <at> gnu.org:
bug#62623; Package guile. (Wed, 19 Apr 2023 10:57:02 GMT) Full text and rfc822 format available.

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

From: Christopher Baines <mail <at> cbaines.net>
To: 62623 <at> debbugs.gnu.org
Subject: Re: bug#62623: (backtrace) hangs and causes excessive memory usage
Date: Wed, 19 Apr 2023 11:54:27 +0100
Someone else has this problem, which makes me feel a bit better since I
had no idea what's going on here.

I'm assuming that (backtrace) causing issues is still a problem with
Guile itself, but it seems like there's some involvement of
guile-fibers (which fits with my experience):

  https://github.com/wingo/fibers/issues/76




This bug report was last modified 343 days ago.

Previous Next


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