unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Peter Wang <ptr.wang@gmail.com>
To: 25156@debbugs.gnu.org
Subject: bug#25156: 26.0.50; `describe-text-properties' hangs with 100% cpu usage when property is a char-table
Date: Sat, 10 Dec 2016 21:59:32 +0800	[thread overview]
Message-ID: <CABpyqyimnLLhsSXK_Vb4o1JynPnhqJNhC4_A_OWbeymj5-fh7w@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]

I came across the problem when I was using `C-u C-x =' on a SLIME
presentation. After some debugging, I found out the cause of the
problem. Here is it:

In a slime REPL buffer, when the evaluation result is rendered, SLIME
adds text properties using `slime-add-presentation-properties'. One
of the text properties is a syntax-table `slime-presentation-syntax-table'.

`C-u C-x =' calls `(describe-char (point))', which in turn calls
`describe-text-properties', which hangs with 100% cpu usage.

I think a possible fix could be done in `describe-property-list', adding
a case in cond to handle the type of syntax-table, something like:


diff --git a/lisp/descr-text.el b/lisp/descr-text.el
index 6c7983a177..926103f35e 100644
--- a/lisp/descr-text.el
+++ b/lisp/descr-text.el
@@ -90,6 +90,7 @@ describe-property-list
       'type 'help-face 'help-args (list value)))
             ((widgetp value)
      (describe-text-widget value))
+            ((syntax-table-p value) (insert "#<syntax table>"))
     (t
      (describe-text-sexp value))))
     (insert "\n")))

[-- Attachment #2: Type: text/html, Size: 1754 bytes --]

             reply	other threads:[~2016-12-10 13:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-10 13:59 Peter Wang [this message]
2016-12-10 14:22 ` bug#25156: 26.0.50; `describe-text-properties' hangs with 100% cpu usage when property is a char-table Eli Zaretskii
2016-12-10 15:03   ` Peter Wang
2016-12-10 15:11     ` Peter Wang
2016-12-10 15:29       ` npostavs
2016-12-10 15:38         ` Peter Wang
2016-12-10 16:04         ` Eli Zaretskii
2016-12-10 16:16           ` Peter Wang
2016-12-10 16:40             ` npostavs

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CABpyqyimnLLhsSXK_Vb4o1JynPnhqJNhC4_A_OWbeymj5-fh7w@mail.gmail.com \
    --to=ptr.wang@gmail.com \
    --cc=25156@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).