From: Linas Vepstas <linasvepstas@gmail.com>
To: 25386@debbugs.gnu.org
Subject: bug#25386: test case update
Date: Sun, 8 Jan 2017 08:57:21 -0600 [thread overview]
Message-ID: <CAHrUA37d+eqS5+bnQS+c3XE5gsbxaE_EV_WMZfrN2q8F8bhFoQ@mail.gmail.com> (raw)
In-Reply-To: <CAHrUA36ZAxeC1nYZQfTLBXGDK1XciNHkEafPuQ+VqzZXASOwcw@mail.gmail.com>
Ran the three test case overnight; saw mostly no increase in mem usage.
-- gc before every thread exit: up to 9M thread exits, no change in heap-size
-- gc before every third thread exit: 25M thread exits, no change.
-- gc before every 17th thread exit: 44M thread exits, relatively
small increase, from (heap-size . 1875902464) to (heap-size .
2068840448)
next prev parent reply other threads:[~2017-01-08 14:57 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 ` Linas Vepstas [this message]
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
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=CAHrUA37d+eqS5+bnQS+c3XE5gsbxaE_EV_WMZfrN2q8F8bhFoQ@mail.gmail.com \
--to=linasvepstas@gmail.com \
--cc=25386@debbugs.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).