From: Andy Wingo <wingo@pobox.com>
To: Linas Vepstas <linasvepstas@gmail.com>
Cc: 25386-done@debbugs.gnu.org
Subject: bug#25386: This can be closed
Date: Wed, 01 Mar 2017 16:31:57 +0100 [thread overview]
Message-ID: <8760jtf1xu.fsf@pobox.com> (raw)
In-Reply-To: <CAHrUA35tZyxVic92LR0No+cnSQkSes7OR39J9iTYOqLs=EEtJw@mail.gmail.com> (Linas Vepstas's message of "Wed, 11 Jan 2017 00:14:14 -0600")
On Wed 11 Jan 2017 07:14, Linas Vepstas <linasvepstas@gmail.com> writes:
> This can be closed as 'fixed'; I tested on today's git
>
> guile (GNU Guile) 2.1.5.19-7e9395
>
> and the worst of it seems to be over. mem usage growth on the
> original test case:
OK, closing :)
Andy
prev parent reply other threads:[~2017-03-01 15:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-07 21:47 bug#25386: guile-2.0 and 2.2 thread leakage+crash; very simple test attached Linas Vepstas
2017-01-08 2:57 ` bug#25386: Manual gc helps Linas Vepstas
2017-01-08 14:57 ` bug#25386: test case update Linas Vepstas
2017-01-08 21:55 ` bug#25386: calling gc too often triggers a crash Linas Vepstas
2017-01-09 1:28 ` bug#25386: Please ignore previous stack trace Linas Vepstas
2017-01-11 6:14 ` bug#25386: This can be closed Linas Vepstas
2017-03-01 15:31 ` Andy Wingo [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=8760jtf1xu.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=25386-done@debbugs.gnu.org \
--cc=linasvepstas@gmail.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.
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).