From: "Gerd Möllmann" <gerd.moellmann@gmail.com>
To: Gregory Heytings <gregory@heytings.org>
Cc: Sam Steingold <sds@gnu.org>, 57751@debbugs.gnu.org
Subject: bug#57751: 29.0.50; crash in GC
Date: Fri, 16 Sep 2022 07:40:07 +0200 [thread overview]
Message-ID: <m28rmjnah4.fsf@Mini.fritz.box> (raw)
In-Reply-To: <b24128855b08d1128dc3@heytings.org> (Gregory Heytings's message of "Thu, 15 Sep 2022 23:17:52 +0000")
Gregory Heytings <gregory@heytings.org> writes:
>>> I could not reproduce that issue here either (Debian bookworm).
>>
>> yes, this is mac-specific
>>
>
> Does it also happen if you turn off the tool bar and the scroll bars?
> And tooltips, maybe?
Should be fixed now.
The crash bisected down to 976965eb5ed00ddc8806b2adcbd5761189823f2c from
a bit more than a week ago. And the reason for the crash was
uninitialized memory, again, aka The Great C Plague. (Which is a lesser
problem in C++ because of default contructors, but I didn't want to
mention that :-).)
What happened is this: The offending commit used an only partly
initialized input_event for frame movements on macOS. So every time
Emacs was too busy to process input events fast enough, and then a GC
happened, the GC would trip over a random value in the movement event.
Sam, could you please confirm it's fixed?
Also, for the Tramp issue you mentioned, I'd recommend to file a bug, if
you didn't already. That sounds like a serious issue to me.
Thanks for the support to all, and thanks to Sam for reporing this.
next prev parent reply other threads:[~2022-09-16 5:40 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 14:37 bug#57751: 29.0.50; crash in GC Sam Steingold
2022-09-13 5:20 ` Gerd Möllmann
2022-09-13 14:51 ` Sam Steingold
2022-09-14 5:46 ` Gerd Möllmann
2022-09-14 18:36 ` Sam Steingold
2022-09-15 5:28 ` Gerd Möllmann
2022-09-15 8:42 ` Gerd Möllmann
2022-09-15 8:48 ` Gerd Möllmann
2022-09-15 10:01 ` Gerd Möllmann
2022-09-15 12:10 ` Eli Zaretskii
2022-09-15 15:12 ` Gerd Möllmann
2022-09-15 16:48 ` Sam Steingold
2022-09-15 22:25 ` Gregory Heytings
2022-09-15 22:41 ` Sam Steingold
2022-09-15 22:42 ` Sam Steingold
2022-09-15 23:17 ` Gregory Heytings
2022-09-16 5:40 ` Gerd Möllmann [this message]
2022-09-19 16:26 ` Sam Steingold
2022-09-20 4:32 ` Gerd Möllmann
2022-09-15 9:23 ` Eli Zaretskii
2022-09-15 9:37 ` Gerd Möllmann
2022-09-15 16:45 ` Sam Steingold
2022-09-15 16:35 ` Sam Steingold
2022-09-14 11:30 ` Gerd Möllmann
2022-09-14 11:32 ` Gerd Möllmann
2022-09-14 18:20 ` Sam Steingold
2022-09-15 4:49 ` Gerd Möllmann
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=m28rmjnah4.fsf@Mini.fritz.box \
--to=gerd.moellmann@gmail.com \
--cc=57751@debbugs.gnu.org \
--cc=gregory@heytings.org \
--cc=sds@gnu.org \
/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).