From: Adam Thompson <firstname.lastname@example.org>
To: Karl Dahlke <email@example.com>
Subject: Re: [Edbrowse-dev] infinite loop
Date: Thu, 20 Feb 2014 20:25:14 +0000 [thread overview]
Message-ID: <20140220202514.GT28870@toaster.adamthompson.me.uk> (raw)
On Thu, Feb 20, 2014 at 10:01:02AM -0500, Karl Dahlke wrote:
> I will respond to some of your other questions in a bit, but first ...
> the hog memory button, as it is today, with jspool = 8, though I don't
> think pool size matters, I push it , get my numbers, get the error;
> then I push it again and edbrowse falls into an infinite spinning loop inside
> The load average jumps up to 1.
> You have to ^| quit to break out.
> Now, even stranger, in buffers .c,
> at line 4346 is jSyncup().
> Just before that put this line in.
> printf("findField returns xx\n", 27);
> It's just a print statement, that's all, but it fixes the infinite loop.
> Even stranger, remove the argument 27 from the print statement,
> it isn't being used anyways, and the infinite loop is back.
> Probably the strangest repeatable thing I've seen in 30 years of programming.
Yeah, that's both weird and concerning.
I've got no idea why this would happen,
particularly as I don't seem to be able to repeat it.
Any idea what the infinite loop is supposed to be doing ?
next prev parent reply other threads:[~2014-02-20 20:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-20 15:01 Karl Dahlke
2014-02-20 20:25 ` Adam Thompson [this message]
2017-01-27 12:43 Karl Dahlke
2017-01-27 14:51 Karl Dahlke
2019-09-10 8:13 [edbrowse-dev] " Karl Dahlke
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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 NNTP newsgroup(s).