From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 59021@debbugs.gnu.org
Subject: bug#59021: Unbounded heap growth when combining dynamic states & delimited continuation
Date: Mon, 07 Nov 2022 16:52:30 -0500 [thread overview]
Message-ID: <87h6zazb35.fsf@gmail.com> (raw)
In-Reply-To: <87leomzr8x.fsf@gmail.com> (Maxim Cournoyer's message of "Mon, 07 Nov 2022 11:03:26 -0500")
Hi,
Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
[...]
> I've tested both 3.0.8 from Guix on multiple machines (including Berlin)
> and 2.2 from Debian 10, and ran the above snippet; it grows initially
> but stabilize quickly and then doesn't budge. I've let it run for more
> than an hour.
Actually, it does grow, it just takes a lot of time. It's now at
150751472 from the original "stable" value of 87846912, so it seems like
an unbound leak after all.
--
Thanks,
Maxim
prev parent reply other threads:[~2022-11-07 21:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-04 18:24 bug#59021: Unbounded heap growth when combining dynamic states & delimited continuation Ludovic Courtès
2022-11-05 22:04 ` Ludovic Courtès
2022-11-20 17:28 ` Ludovic Courtès
2022-11-07 16:03 ` Maxim Cournoyer
2022-11-07 21:52 ` Maxim Cournoyer [this message]
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h6zazb35.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=59021@debbugs.gnu.org \
--cc=ludo@gnu.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).