From: asjo@koldfront.dk (Adam Sjøgren)
Subject: XEmacs 21.4 p16, seemingly endless, cpu-consuming loop in string-match?!
Date: Sun, 19 Dec 2004 15:28:29 +0100 [thread overview]
Message-ID: <87u0qibbw2.fsf@koldfront.dk> (raw)
Hi.
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.
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.
Any ideas?
XEmacs 21.4 (patch 16) "Corporate Culture" [Lucid]
(i386-debian-linux, Mule) of Sun Dec 12 2004 on penell
No Gnus v0.3 (update from cvs yesterday and re-bytecompiled)
Best regards,
--
"Snurra min jord igen" Adam Sjøgren
asjo@koldfront.dk
next reply other threads:[~2004-12-19 14:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-19 14:28 Adam Sjøgren [this message]
2004-12-20 5:20 ` Katsumi Yamaoka
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=87u0qibbw2.fsf@koldfront.dk \
--to=asjo@koldfront.dk \
/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).