From: Eli Zaretskii <eliz@gnu.org>
To: Richard Copley <rcopley@gmail.com>
Cc: 25279@debbugs.gnu.org
Subject: bug#25279: 26.0.50; Slowdown/crash on certain characters
Date: Tue, 27 Dec 2016 09:21:46 +0200 [thread overview]
Message-ID: <83lgv1x2et.fsf@gnu.org> (raw)
In-Reply-To: <CAPM58ohq=_YMqPJuD3+WqtVfrCOO=RGNVY_cGtjUOM0n-Co7=g@mail.gmail.com> (message from Richard Copley on Mon, 26 Dec 2016 21:21:57 +0000)
> From: Richard Copley <rcopley@gmail.com>
> Date: Mon, 26 Dec 2016 21:21:57 +0000
> Cc: 25279@debbugs.gnu.org
>
> > A crash shouldn't happen in any case, so if you can show a recipe and
> > a backtrace, maybe this could be fixed.
> >
> > Thanks.
>
> Reproducing the slowness and high CPU consumption is easy.
>
> The "crash" I referred to is probably better termed a "hang" (as
> far as I can see an indefinite one), sorry. I don't know a simple
> recipe, but if you use Emacs in this state for long enough, it
> usually hangs eventually.
Is it a hang, or just some long and very busy loop? E.g., if you set
garbage-collection-messages to a non-nil value, do you see periodic
announcements of GC during the "hang"? And if you go for a coffee,
does Emacs eventually recover and starts responding again? What if
you type M-< or M-> to force the problematic characters out of the
displayed portion of the buffer -- does Emacs recover then?
> Recipe:
> Uninstall Symbola (but perhaps other font changes are required).
It isn't easy to uninstall fonts from a running system, because they
are usually in use by some application. So reproducing this will be
hard for me, as I have Symbola installed everywhere. I will try to
find such a system, but no promises.
> Below are C call stacks obtained from a hung emacs process
> by attaching gdb to it.
Is it possible for you to try to figure out what is the looping stack
frame, by following the advice in etc/DEBUG, under "If the symptom of
the bug is that Emacs fails to respond"?
> Possibly a clue:
> While I had the hung emacs process stopped in GDB I started a
> new Emacs process to edit this email and the new Emacs was
> also horribly slow! When I killed the process in the debugger,
> the new Emacs recovered to normal speed.
Attaching a debugger to Emacs built from the master branch causes such
problems due to the low-level keyboard hook in Emacs. (We avoid that
problem when Emacs is started from GDB to begin with.) So I don't
think this is relevant to the issue at hand.
Thanks.
next prev parent reply other threads:[~2016-12-27 7:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-26 20:09 bug#25279: 26.0.50; Slowdown/crash on certain characters Richard Copley
2016-12-26 20:18 ` Richard Copley
2016-12-26 20:25 ` Eli Zaretskii
2016-12-26 20:40 ` Richard Copley
2016-12-26 20:49 ` Eli Zaretskii
2016-12-26 21:21 ` Richard Copley
2016-12-27 7:21 ` Eli Zaretskii [this message]
[not found] ` <CAPM58oiS8+TuR8WhKZmEZdWY_ac44xLDjnpYAD0aWqU6=mX7eg@mail.gmail.com>
2016-12-27 13:51 ` bug#25279: Fwd: " Richard Copley
[not found] ` <CAPM58oioMPAo=x8F1whs5YS3RMwceoadAT9TN7Macbx=SaxyJA@mail.gmail.com>
2016-12-27 13:53 ` Richard Copley
[not found] ` <838tr1wlg4.fsf@gnu.org>
[not found] ` <CAPM58og6d1EqTEyMy6df27DXB_ERYOD5=pmFHC9MmoFmq+CDgw@mail.gmail.com>
[not found] ` <837f6lwkju.fsf@gnu.org>
2016-12-27 14:06 ` Richard Copley
2016-12-27 14:15 ` Eli Zaretskii
2016-12-27 14:32 ` Richard Copley
2016-12-27 21:15 ` Richard Copley
2017-02-21 20:05 ` Richard Copley
2017-02-21 20:28 ` Eli Zaretskii
2017-02-21 20:33 ` Richard Copley
2017-02-21 20:38 ` Richard Copley
2017-02-23 16:19 ` Eli Zaretskii
2017-02-23 19:15 ` Richard Copley
2017-02-23 19:20 ` Richard Copley
2017-02-23 15:22 ` Eli Zaretskii
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=83lgv1x2et.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=25279@debbugs.gnu.org \
--cc=rcopley@gmail.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.