From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Alan Mackenzie <acm@muc.de>
Cc: 10664@debbugs.gnu.org
Subject: bug#10664: 24.0.93; JIT font-lock infloops in a C file
Date: Mon, 06 Feb 2012 09:39:26 -0500 [thread overview]
Message-ID: <jwvzkcwc9kz.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <20120206110957.GA2731@acm.acm> (Alan Mackenzie's message of "Mon, 6 Feb 2012 11:09:57 +0000")
>> > I don't have a recipe starting from "emacs -Q", sorry.
>> > I left my freshly built Emacs 24.0.93 running, and when I returned to
>> > it a few hours later, I found it unresponsive, endlessly showing in
>> > the echo area "JIT lock socket.c", interspersed with GC messages
>> > (I have garbage-collection-messages set non-nil).
>> > Breaking into Emacs with a debugger produced the backtrace below (it's
>> > an optimized build, so the backtrace may be inaccurate, sorry). I
>> > attach the file socket.c (part of the Guile sources) as well.
> I got something similar for this socket.c. I load it into emacs -Q, then
> start scrolling downwards, a page at a time. The first five scrolls are
> fine. Then it hangs on the sixth.
While not easy, it should be theoretically possible to reproduce the
problem with (setq font-lock-support-mode nil) which would make it much
easier to debug. If the problem doesn't appear right when enabling
font-lock, then it needs to be triggered by cutting and re-inserting
a chunk of text (and you need to find a chunk that triggers the problem).
Stefan
next prev parent reply other threads:[~2012-02-06 14:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 18:23 bug#10664: 24.0.93; JIT font-lock infloops in a C file Eli Zaretskii
2012-02-05 18:18 ` Eli Zaretskii
2012-02-06 11:09 ` Alan Mackenzie
2012-02-06 14:39 ` Stefan Monnier [this message]
2012-02-06 17:04 ` Eli Zaretskii
2012-02-07 17:30 ` Eli Zaretskii
2012-02-07 19:20 ` Alan Mackenzie
2012-02-07 20:58 ` Eli Zaretskii
2012-02-07 21:34 ` Alan Mackenzie
2012-02-07 23:39 ` Stefan Monnier
2012-02-08 11:47 ` Alan Mackenzie
2012-02-08 17:49 ` Eli Zaretskii
2012-02-08 19:28 ` Stefan Monnier
2012-02-10 11:28 ` Alan Mackenzie
2012-02-12 20:57 ` Eli Zaretskii
2012-02-14 5:42 ` Chong Yidong
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=jwvzkcwc9kz.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=10664@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).