From: Peter Wang <ptr.wang@gmail.com>
To: npostavs@users.sourceforge.net
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 23:38:34 +0800 [thread overview]
Message-ID: <CABpyqyjONebL=6UVzpumc6O0uGdvhuUBtQQ0DamJNYpnhmNh1A@mail.gmail.com> (raw)
In-Reply-To: <87h96ber9z.fsf@users.sourceforge.net>
[-- Attachment #1: Type: text/plain, Size: 1051 bytes --]
Indeed, I got the same result as you did from emacs -Q. I will look into my
configuration and provide more information. Thanks!
On Sat, Dec 10, 2016 at 11:29 PM, <npostavs@users.sourceforge.net> wrote:
> Peter Wang <ptr.wang@gmail.com> writes:
>
> > BTW, I also found that `describe-variable' has the same problem.
> >
> > (describe-variable 'lisp-mode-syntax-table)
> >
> > I have not looked into this yet, it could be the same bug.
> >
> > On Sat, Dec 10, 2016 at 11:03 PM, Peter Wang <ptr.wang@gmail.com> wrote:
> >
> > A simplest test case is like:
> >
> > (describe-property-list (list 'syntax-table lisp-mode-syntax-table))
> >
> > evaluating this Elisp expression will hang with 100% CPU usage.
>
> Neither of these hang for me from emacs -Q, using latest master
> (fc0fd24c105b)
>
> (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)"
>
>
[-- Attachment #2: Type: text/html, Size: 1626 bytes --]
next prev parent reply other threads:[~2016-12-10 15:38 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 [this message]
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='CABpyqyjONebL=6UVzpumc6O0uGdvhuUBtQQ0DamJNYpnhmNh1A@mail.gmail.com' \
--to=ptr.wang@gmail.com \
--cc=25156@debbugs.gnu.org \
--cc=npostavs@users.sourceforge.net \
/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).