From: Robert Pluim <rpluim@gmail.com>
To: 20825@debbugs.gnu.org
Subject: bug#20825: 25.0.50; Cannot view info docs anymore (100% CPU)
Date: Tue, 16 Jun 2015 14:18:33 +0200 [thread overview]
Message-ID: <87eglbu9ra.fsf@gmail.com> (raw)
In-Reply-To: <87h9q8jfn4.fsf@gnu.org>
Tassilo Horn <tsdh@gnu.org> writes:
> With emacs HEAD e80225000dda3f1deac5ea95a9253301b05fbed7, emacs starts
> using up 100% CPU time when trying to view some info documentation.
>
> 1. emacs -Q
> 2. C-h i
> The info index is shown properly
> 3. m emacs RET
>
I see this as well.
> Now emacs starts using up 100% CPU, and the emacs info docs aren't
> shown. With `debug-on-quit' I obtain the following backtrace during the
> hang.
>
> Debugger entered--Lisp error: (quit)
> count-lines(1 1)
> line-number-at-pos(70)
> filepos-to-bufferpos(1116 approximate)
> Info-find-node-2("/home/horn/Repos/el/emacs/info/emacs" "Top" nil nil)
> Info-find-node("emacs" "Top" nil nil)
> Info-goto-node("(emacs)" nil)
> Info-menu("Emacs" nil)
> funcall-interactively(Info-menu "Emacs" nil)
> call-interactively(Info-menu nil nil)
> command-execute(Info-menu)
>
Not unsurprisingly, git bisect points at this commit as the culprit:
commit b95f53f0383b5df82e0b711f5027881950893f4f
Author: Stefan Monnier <monnier@iro.umontreal.ca>
Date: Mon Jun 15 18:48:08 2015 -0400
* lisp/info.el: Cleanup bytepos/charpos issues
* lisp/international/mule-util.el: Use lexical-binding.
(filepos-to-bufferpos): New function.
* lisp/info.el (Info-find-in-tag-table-1): Use 0-based file positions.
(Info-find-node-2): Use filepos-to-bufferpos (bug#20704).
(Info-read-subfile, Info-search): Use 0-based file positions.
and updating to the commit just before makes the issue go away.
Robert
next prev parent reply other threads:[~2015-06-16 12:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 7:06 bug#20825: 25.0.50; Cannot view info docs anymore (100% CPU) Tassilo Horn
2015-06-16 12:18 ` Robert Pluim [this message]
2015-06-16 14:38 ` 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=87eglbu9ra.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=20825@debbugs.gnu.org \
--cc=bug-gnu-emacs@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 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.