unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eval Exec <execvy@gmail.com>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: [MPS-test] scratch/igc branch (commit: 42731228d24) crashed
Date: Mon, 5 Aug 2024 23:48:36 +0800	[thread overview]
Message-ID: <CAKfPJDr7Df-KfATpHKv9HFtmLGFXW5EgD_n4=w80Q6VwF5TQ6w@mail.gmail.com> (raw)
In-Reply-To: <m25xsf7z3c.fsf@pro2.fritz.box>

>  Are you using master without MPS otherwise, and can compare the two?
I will try to using master without MPS later.

Now I compiled scratch/igc with --with-x-toolkit=gtk3, and emacs won't
crash anymore.
When I compile scratch/igc with --with-x-toolkit=lucid, and with
(scroll-bar-mode t), emacs won't crash.
When I compile scratch/igc with --with-x-toolkit=lucid, and with
(scroll-bar-mode -1), emacs will crash.

On Mon, Aug 5, 2024 at 11:45 PM Gerd Möllmann <gerd.moellmann@gmail.com> wrote:
>
> Eval Exec <execvy@gmail.com> writes:
>
> >> Or describe how to reproduce this
> >
> > I'm not sure how to reproduce this, but it seems to happen sometimes
> > when I open a Rust file in lsp-mode. When I start typing, the Corfu
> > completion popup appears with candidate suggestions. Occasionally, the
> > Corfu popup will freeze, causing Emacs to freeze as well, and then
> > Emacs crashes after about a second.
>
> Hm. Can't do much here, I'm afraid.
>
> The location of the error in pixel_something is unusual for a GC-related
> error, haven't seen something like that before. Are you using master
> without MPS otherwise, and can compare the two?



  reply	other threads:[~2024-08-05 15:48 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-05 15:00 [MPS-test] scratch/igc branch (commit: 42731228d24) crashed Eval Exec
2024-08-05 15:12 ` Gerd Möllmann
2024-08-05 15:18   ` Eval Exec
2024-08-05 15:34     ` Gerd Möllmann
2024-08-05 15:20   ` Eval Exec
2024-08-05 15:45     ` Gerd Möllmann
2024-08-05 15:48       ` Eval Exec [this message]
2024-08-05 15:55         ` Eval Exec
2024-08-05 16:14       ` Eval Exec
2024-08-05 15:29 ` Eli Zaretskii
2024-08-05 15:33   ` Eval Exec
2024-08-05 15:47   ` Gerd Möllmann
2024-08-05 15:54     ` Eli Zaretskii
2024-08-05 16:01       ` Gerd Möllmann
2024-08-05 16:20 ` Pip Cet
2024-08-05 16:40   ` Pip Cet
2024-08-05 16:50     ` Eval Exec
2024-08-05 17:45     ` Eli Zaretskii
2024-08-05 18:00       ` Pip Cet
2024-08-05 18:19         ` Eli Zaretskii
2024-08-08 16:56     ` Eval Exec

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='CAKfPJDr7Df-KfATpHKv9HFtmLGFXW5EgD_n4=w80Q6VwF5TQ6w@mail.gmail.com' \
    --to=execvy@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=gerd.moellmann@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).