From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Andy Wingo <wingo@igalia.com>, help-guix@gnu.org, 27476@debbugs.gnu.org
Subject: bug#27476: guix pull fails on powerful server
Date: Tue, 29 Jan 2019 11:07:15 +0100 [thread overview]
Message-ID: <8736pbrd4c.fsf__7496.06009792245$1548757458$gmane$org@elephly.net> (raw)
In-Reply-To: <87h8nstms1.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> ludo@gnu.org (Ludovic Courtès) skribis:
>
>> I can’t reproduce this with current Guile ‘stable-2.2’, following Andy’s
>> weak-table rewrite¹, so this might have been a weak-table bug showing up
>> under memory pressure.
>
> With Guile 2.2.3 a similar program triggers a crash very quickly:
>
> --8<---------------cut here---------------start------------->8---
> $ cat ../guile-debugging/syntax-parms.scm
> (use-modules (ice-9 threads)
> (srfi srfi-1)
> (guix monads)
> (guix store)
> (system base compile))
>
> (compile #f) ;load modules
>
> (define threads
> (unfold (lambda (x) (> x 100))
> (lambda (x)
> (call-with-new-thread
> (lambda ()
> (while #t
> (compile
> '(mlet %store-monad ((x y))
> (mbegin %store-monad
> (return x)
> (return y)))
> #:env (current-module)
> #:from 'scheme
> #:to 'tree-il)))))
> 1+
> 0))
>
> (for-each join-thread threads)
[…]
> --8<---------------cut here---------------end--------------->8---
I tried this with guile 2.2.4 on my laptop with 4 CPUs (according to
lscpu) and I did not get a crash even after waiting for several minutes.
--
Ricardo
next prev parent reply other threads:[~2019-01-29 10:24 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-22 8:38 guix pull fails on powerful server Ricardo Wurmus
2017-09-22 14:10 ` bug#27476: " Ludovic Courtès
2017-09-25 7:27 ` Andy Wingo
2017-09-25 13:03 ` Ludovic Courtès
2017-09-25 14:02 ` bug#27476: " Ricardo Wurmus
2017-09-30 7:59 ` Ricardo Wurmus
2017-09-30 7:59 ` Ricardo Wurmus
2017-10-03 20:29 ` bug#27476: " Marius Bakke
2017-10-03 20:29 ` Marius Bakke
2017-10-04 13:15 ` bug#27476: " Ricardo Wurmus
2017-10-04 13:15 ` Ricardo Wurmus
2017-10-04 15:09 ` bug#27476: " Clément Lassieur
2017-10-04 15:09 ` Clément Lassieur
2017-10-04 16:17 ` bug#27476: " Ricardo Wurmus
2017-10-07 15:11 ` Ludovic Courtès
2017-10-10 7:17 ` Ricardo Wurmus
2017-10-10 11:32 ` Ludovic Courtès
2017-10-10 11:32 ` bug#27476: " Ludovic Courtès
2017-10-10 7:17 ` Ricardo Wurmus
2017-10-07 15:11 ` Ludovic Courtès
2017-10-12 13:37 ` Ludovic Courtès
2017-10-13 20:29 ` Ricardo Wurmus
2017-10-13 20:29 ` Ricardo Wurmus
2017-10-13 21:04 ` Ricardo Wurmus
2017-10-13 21:10 ` Ricardo Wurmus
2017-10-12 13:37 ` Ludovic Courtès
2017-11-07 10:57 ` Ludovic Courtès
2018-04-30 21:19 ` Ludovic Courtès
2018-04-30 21:39 ` bug#27476: libguile/memoize.c is not thread safe, so syntax parameter expansion is not thread-safe Ludovic Courtès
2018-05-09 8:41 ` Andy Wingo
2018-05-09 9:23 ` Ludovic Courtès
2018-05-09 10:18 ` Andy Wingo
2019-02-06 14:48 ` Ludovic Courtès
2019-02-06 16:14 ` Andy Wingo
2019-02-06 22:09 ` Ludovic Courtès
2019-01-29 10:07 ` Ricardo Wurmus [this message]
2019-01-29 10:07 ` bug#27476: guix pull fails on powerful server Ricardo Wurmus
2017-11-07 10:57 ` Ludovic Courtès
2017-09-25 13:03 ` Ludovic Courtès
2017-09-25 8:43 ` Clément Lassieur
2017-09-25 8:43 ` Clément Lassieur
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='8736pbrd4c.fsf__7496.06009792245$1548757458$gmane$org@elephly.net' \
--to=rekado@elephly.net \
--cc=27476@debbugs.gnu.org \
--cc=help-guix@gnu.org \
--cc=ludo@gnu.org \
--cc=wingo@igalia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.