From: Toon Claes <toon@tonotdo.com>
To: Alan Mackenzie <acm@muc.de>
Cc: 10652@debbugs.gnu.org
Subject: bug#10652: font-lock very slow for C++
Date: Mon, 02 Apr 2012 09:48:12 +0200 [thread overview]
Message-ID: <3cd3c01ead9ed4dc9ceca684516e88d3@tonotdo.com> (raw)
In-Reply-To: <20120329220026.GC2594@acm.acm>
[-- Attachment #1: Type: text/plain, Size: 1583 bytes --]
Hi Alan,
emacs hangs for hours. Luckily it only used one of my 4
processor cores, so I could leave it loading in the background.
This
is what I've done:
Open the file, in c++-mode, and scroll to
end-of-buffer (M->). The mouse cursor starts spinning, but the end of
buffer is not shown.
When I press C-g three times, the end of the
buffer is shown. The fontification looks correct.
When I go back to
beginning-of-buffer, same problem.
When I press M->, M-< several
times, I cannot recover with C-g and I need to kill emacs:-(
isearch
works fine with font-lock-mode disabled.
Even, depending on the
position in the buffer, it happens the command M-x font-lock-mode gives
the spinning mouse cursor. Again 3x C-g solves this.
So I can say
pretty sure, font-lock-mode is causing the "delay".
I've tested again
with the bazaar version of last friday.
My test file contains
something like this:
int ClassName::MethodAbc(void)
{
SOME_PRETEST_MACRO;
return TranslateResult(LibFunctionAbc(m_Member));
}
And this repeated for something like 20 times (of course with
different names, and with different parameters).
The macro is
something like:
#define SOME_PRETEST_MACRO if (!Ready()) return -1;
With this test file, I could easily reproduce the problem.
I hope
this can help investigating the issue.
Toon
On 2012-03-30 00:00,
Alan Mackenzie wrote:
> Hello, Toon.
>
> On Thu, Mar 29, 2012 at
09:46:03PM +0200, Toon Claes wrote:
>
>> Hi Alan,
>
>> About: (i) yes
I've tried that, emacs -Q didn't make a difference
>
> Worth knowing
[-- Attachment #2: Type: text/html, Size: 4145 bytes --]
prev parent reply other threads:[~2012-04-02 7:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 11:15 bug#10652: 24.0.93; font-lock very slow for C++ Helmut Eller
2012-02-26 9:47 ` Chong Yidong
2012-03-01 19:36 ` Alan Mackenzie
2012-03-02 22:27 ` Alan Mackenzie
2012-03-16 14:19 ` Alan Mackenzie
2012-03-14 9:45 ` bug#10652: " Toon Claes
2012-03-16 10:18 ` bug#10652: Recursive loop in alloc.c [ Was: font-lock very slow for C++ ] Alan Mackenzie
[not found] ` <20120316101838.GB3439@acm.acm>
2012-03-16 10:34 ` Andreas Schwab
2012-03-16 14:24 ` bug#10652: 24.0.93; font-lock very slow for C++ Alan Mackenzie
2012-03-28 7:07 ` bug#10652: " Toon Claes
2012-03-29 9:35 ` Alan Mackenzie
2012-03-29 19:46 ` Toon Claes
2012-03-29 22:00 ` Alan Mackenzie
2012-04-02 7:48 ` Toon Claes [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=3cd3c01ead9ed4dc9ceca684516e88d3@tonotdo.com \
--to=toon@tonotdo.com \
--cc=10652@debbugs.gnu.org \
--cc=acm@muc.de \
/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).