From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] crash while sup is sitting idle
Date: Tue, 01 Apr 2008 10:13:23 -0700 [thread overview]
Message-ID: <1207069973-sup-4350@south> (raw)
In-Reply-To: <1207068663-sup-6170@ln>
Reformatted excerpts from Michael Gurski's message of 2008-04-01:
> 13G free on that partition, quite a bit of memory free as well, both
> real and swap. I can more or less get it to happen consistently if I
> try to load 4+ pages of unread messages at a time. It might be more
> needed now, as it's been several days since I've tried it.
And which git branch, master or next?
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2008-04-01 17:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-29 3:03 Michael Gurski
2008-04-01 15:35 ` William Morgan
2008-04-01 16:52 ` Michael Gurski
2008-04-01 17:13 ` William Morgan [this message]
2008-04-01 19:50 ` Michael Gurski
2008-04-01 20:03 ` Christopher Warrington
2008-04-03 1:43 ` William Morgan
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=1207069973-sup-4350@south \
--to=wmorgan-sup@masanjin.net \
/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