From: Eli Zaretskii <eliz@gnu.org>
To: Mikael Svahnberg <Mikael.Svahnberg@bth.se>
Cc: 43882@debbugs.gnu.org
Subject: bug#43882: 27.1; Gnus sometimes crashes emacs 27.1 during nnir search
Date: Fri, 09 Oct 2020 17:35:40 +0300 [thread overview]
Message-ID: <83v9fj5uwz.fsf@gnu.org> (raw)
In-Reply-To: <m2pn5rzoxx.fsf@bth.se> (message from Mikael Svahnberg on Fri, 09 Oct 2020 12:14:18 +0200)
> From: Mikael Svahnberg <Mikael.Svahnberg@bth.se>
> Date: Fri, 09 Oct 2020 12:14:18 +0200
>
>
> I upgraded to emacs 27.1 yesterday and so far it has crashed twice on me
> when I search for emails in Gnus. I use the following function to
> perform the search (there are probably better ways, but this has worked
> for me the past eight years):
>
> --------------------
> ;; Search mail from everywhere
> (defun msv-search-mail ()
> (interactive)
> (with-current-buffer "*Group*"
> (save-excursion
> (beginning-of-buffer)
> (search-forward "All Mail")
> (call-interactively (gnus-group-make-nnir-group nil)))))
>
> ;; <2017-08-15 Tue>
> ;; Try a better search input
> (use-package gnus-x-gm-raw :ensure t)
> --------------------
>
> What happens is that emacs freezes and (I happened to have =top=
> running in a terminal nearby) consumes 100% CPU for 5-10 seconds, before
> crashing.
Looks like stack overflow during GC? What is the maximum size of the
stack of the running Emacs process? Can you try enlarging it?
next prev parent reply other threads:[~2020-10-09 14:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 10:14 bug#43882: 27.1; Gnus sometimes crashes emacs 27.1 during nnir search Mikael Svahnberg
2020-10-09 14:35 ` Eli Zaretskii [this message]
2020-10-09 14:43 ` Robert Pluim
2020-10-12 7:12 ` Mikael Svahnberg
2020-10-12 9:45 ` Robert Pluim
2020-10-15 7:26 ` Mikael Svahnberg
2020-10-20 13:11 ` Mikael Svahnberg
2020-10-20 17:01 ` Eric Abrahamsen
2020-10-21 6:41 ` Mikael Svahnberg
2020-10-21 18:23 ` Eric Abrahamsen
2022-04-30 17:27 ` Lars Ingebrigtsen
[not found] ` <m2zgk0h3rh.fsf@bth.se>
2022-05-02 8:31 ` Lars Ingebrigtsen
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=83v9fj5uwz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=43882@debbugs.gnu.org \
--cc=Mikael.Svahnberg@bth.se \
/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).