unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: npostavs@users.sourceforge.net
To: Peter Wang <ptr.wang@gmail.com>
Cc: 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 11:40:31 -0500	[thread overview]
Message-ID: <87eg1feo00.fsf@users.sourceforge.net> (raw)
In-Reply-To: <CABpyqyj3xaF_AsiOFj_7yv+DMtGBf9ySDqx7ZmsuF30R8jrHJw@mail.gmail.com> (Peter Wang's message of "Sun, 11 Dec 2016 00:16:29 +0800")

# not an Emacs bug
tags 25156 notabug
close 25156
quit

Peter Wang <ptr.wang@gmail.com> writes:

> I found the culprit was this line in my configuration:
>
> (setq lisp-indent-function 'common-lisp-indent-function)
>
> and common-lisp-indent-function is provided by 
>
> `.emacs.d/elpa/slime-20161109.640/contrib/slime-cl-indent.el'
>
> I think it is a wrong configuration. 
>
> something in common-lisp-indent-function cause the huge slowing down.

Okay, looks like a problem with slime-cl-indent.el then.  Using Emacs'
common-lisp-indent-function (from lisp/emacs-lisp/cl-indent.el) I get
around 4 seconds, so it's slower but not a hang.

>  >
>  > (benchmark 1 '(describe-variable 'lisp-mode-syntax-table)) ;=> "Elapsed time: 1.272053s (0.161946s in 6 GCs)"
>  > (benchmark 1 '(describe-property-list (list 'syntax-table lisp-mode-syntax-table))) ;=> "Elapsed time: 1.165824s (0.139516s in 5 GCs)"





      reply	other threads:[~2016-12-10 16:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-10 13:59 bug#25156: 26.0.50; `describe-text-properties' hangs with 100% cpu usage when property is a char-table Peter Wang
2016-12-10 14:22 ` 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 [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

  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=87eg1feo00.fsf@users.sourceforge.net \
    --to=npostavs@users.sourceforge.net \
    --cc=25156@debbugs.gnu.org \
    --cc=ptr.wang@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 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).