From: Linas Vepstas <linasvepstas@gmail.com>
To: Andy Wingo <wingo@pobox.com>
Cc: 19676@debbugs.gnu.org
Subject: bug#19676: madvise bug in guile-git
Date: Mon, 20 Jun 2016 18:36:51 -0500 [thread overview]
Message-ID: <CAHrUA37wsD7O2d7Y69qUkzgPc25Agr58+DVKQuz1xBA_ZMOptw@mail.gmail.com> (raw)
In-Reply-To: <87bn2vho22.fsf@pobox.com>
[-- Attachment #1: Type: text/plain, Size: 488 bytes --]
On Mon, Jun 20, 2016 at 10:34 AM, Andy Wingo <wingo@pobox.com> wrote:
> On Sat 24 Jan 2015 23:52, Linas Vepstas <linasvepstas@gmail.com> writes:
>
> > I've got a test where hit guile with maybe a dozen threads doing
> > assorted things. Doing this, I then see handful of these messages:
> > "madvise failed: Cannot allocate memory" every 5 or 10 seconds.
>
> Do you still get this with Guile 2.1.3?
Building current git now; setup to reproduce this issue will be difficult.
--linas
[-- Attachment #2: Type: text/html, Size: 999 bytes --]
next prev parent reply other threads:[~2016-06-20 23:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-24 22:52 bug#19676: madvise bug in guile-git Linas Vepstas
2016-06-20 15:34 ` Andy Wingo
2016-06-20 23:36 ` Linas Vepstas [this message]
2016-06-21 7:52 ` Andy Wingo
2016-06-21 13:28 ` Linas Vepstas
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=CAHrUA37wsD7O2d7Y69qUkzgPc25Agr58+DVKQuz1xBA_ZMOptw@mail.gmail.com \
--to=linasvepstas@gmail.com \
--cc=19676@debbugs.gnu.org \
--cc=wingo@pobox.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).