From: Eli Zaretskii <eliz@gnu.org>
To: rswgnu@gmail.com
Cc: acm@muc.de, pillowtrucker@proton.me, 70423@debbugs.gnu.org
Subject: bug#70423: 29.3; cc-mode hang at 100% cpu and consuming all available memory
Date: Thu, 02 May 2024 11:40:46 +0300 [thread overview]
Message-ID: <86jzkcmws1.fsf@gnu.org> (raw)
In-Reply-To: <CA+OMD9j8+37jLsg6qdtR+SV2tsMYCy9--2Zs7YCmSFOc=-dUHg@mail.gmail.com> (message from Robert Weiner on Sat, 20 Apr 2024 11:52:49 -0400)
> From: Robert Weiner <rsw@gnu.org>
> Date: Sat, 20 Apr 2024 11:52:49 -0400
> Cc: pillowtrucker@proton.me, 70423@debbugs.gnu.org,
> Eli Zaretskii <eliz@gnu.org>
>
> I have now read through the recent messages more carefully, duplicated the hang in c++-mode using
> pillowtrucker's init.el and his drm_formats.cpp file simply by invoking M->. I then added both Alan's cc-defs.el
> fix and his new c++-defun-prompt-regexp and that resolved the hang. If I add the new c++ regexp without the
> cc-defs.el fix, that also seems to solve the hang. So I retract my prior message and acknowledge one source
> of the problem has been the existing Hyperbole regexps. We'll update Hyperbole to use Allen's new regexps
> and hopefully this will close this issue after pillowtrucker does some testing. (I think Allen's other fixes should
> be applied to and that they will help performance).
Thanks.
Should this bug be closed, then? I believe you are saying that the
left-overs, such as they are, are not in Emacs?
next prev parent reply other threads:[~2024-05-02 8:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-16 13:36 bug#70423: 29.3; cc-mode hang at 100% cpu and consuming all available memory 1stmil.eth via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-16 15:52 ` bug#70423: Possible workaround/culprit pillowtrucker--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-16 18:31 ` Dmitry Gutov
2024-04-16 16:22 ` bug#70423: 29.3; cc-mode hang at 100% cpu and consuming all available memory Eli Zaretskii
2024-04-16 17:05 ` Alan Mackenzie
2024-04-16 17:59 ` Alan Mackenzie
2024-04-16 19:51 ` pillowtrucker--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-18 18:39 ` Alan Mackenzie
2024-04-19 20:49 ` pillowtrucker--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-20 9:22 ` Alan Mackenzie
2024-04-20 13:14 ` Robert Weiner
2024-04-20 15:52 ` Robert Weiner
2024-05-02 8:40 ` Eli Zaretskii [this message]
2024-05-02 22:01 ` Robert Weiner
2024-05-03 5:54 ` 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
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=86jzkcmws1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=70423@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=pillowtrucker@proton.me \
--cc=rswgnu@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).