From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: XEmacs 21.4 p16, seemingly endless, cpu-consuming loop in string-match?!
Date: Mon, 20 Dec 2004 14:20:52 +0900 [thread overview]
Message-ID: <b9yd5x57dfv.fsf@jpl.org> (raw)
In-Reply-To: <87u0qibbw2.fsf@koldfront.dk>
>>>>> In <87u0qibbw2.fsf@koldfront.dk> Adam Sjøgren wrote:
> Recently Debian unstable got new XEmacs packages. Since then, I think,
> xemacs on my machine often enters a seemingly endless, cpu-consuming
> loop when I enter a group or try to read an article.
I experienced the same problem by XEmacs of the versions before
and after releasing 21.4.16. It makes it hard to test Gnus and
some ELisp packages with it.
> When I kill the xemacs process (after say 5 minutes of burning cpu on
> a P4 2.4 GHz), I always get a backtrace that starts with:
> Lisp backtrace follows:
> string-match("=\\?\\([^][- ()<>@,;:*\\\"/?.=]+\\)\\(?:\\*[^?]+\\)?\\?\\(B\\|Q\\)\\?\\([!->@-~ ]*\\)\\?=" "=?iso-8859-1?Q?Sj=F8gren?=")
> # bind (word)
> rfc2047-parse-and-decode("=?iso-8859-1?Q?Sj=F8gren?=")
> # (unwind-protect ...)
> (The actual string is different, sometimes it is the From:, other
> times it is the Subject: - it has, so far, always been encoded).
> It doesn't happen every time I enter the same group/read the same
> article, only sometimes. Which is, of course, rather troubling.
I'm not sure whether it is related to neither the regexp
matching nor the rfc2047 decoder. I recommend you to go to the
xemacs-beta list if you still want to continue using XEmacs. I
lost interest to that long ago. Sorry.
prev parent reply other threads:[~2004-12-20 5:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-19 14:28 Adam Sjøgren
2004-12-20 5:20 ` Katsumi Yamaoka [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b9yd5x57dfv.fsf@jpl.org \
--to=yamaoka@jpl.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 NNTP newsgroup(s).