From: Alan Third <alan@idiocy.org>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: 45541@debbugs.gnu.org
Subject: bug#45541: 28.0.50; Frequent crashes on ARM macOS
Date: Wed, 30 Dec 2020 15:22:32 +0000 [thread overview]
Message-ID: <X+ybOEjxGVomdFGM@breton.holly.idiocy.org> (raw)
In-Reply-To: <CAArVCkSRbEjYNgMWKfUHbJxFugwMrx9MViN+XHDMgqC9W5QmTg@mail.gmail.com>
On Wed, Dec 30, 2020 at 03:53:01PM +0100, Philipp Stephani wrote:
> Am Mi., 30. Dez. 2020 um 15:49 Uhr schrieb Philipp Stephani
> <p.stephani2@gmail.com>:
> >
> > Am Mi., 30. Dez. 2020 um 15:42 Uhr schrieb Philipp Stephani
> > <p.stephani2@gmail.com>:
> > >
> > > Am Mi., 30. Dez. 2020 um 15:05 Uhr schrieb Alan Third <alan@idiocy.org>:
> > > >
> > > > On Wed, Dec 30, 2020 at 02:01:18PM +0100, Philipp Stephani wrote:
> > > > > Am Mi., 30. Dez. 2020 um 01:10 Uhr schrieb Alan Third <alan@idiocy.org>:
> > > > > >
> > > > > > On Tue, Dec 29, 2020 at 11:32:43PM +0100, Philipp wrote:
> > > > > > >
> > > > > > > With an Emacs built from the emacs-27 branch I get frequent crashes on
> > > > > > > ARM64 macOS (Big Sur). I haven't managed to produce an Elisp stacktrace
> > > > > > > yet, but here's the crash report:
> > > > > > <snip>
> > > > > > > Looks like a crash in ns_mouse_position.
> > > > > >
> > > > > > Can you check that the build includes this?
> > > > > >
> > > > > > 6aa9fe3e1b4052b2acde86404a90e35893ebfa00?
> > > > > > Fix crash in ns_mouse_position (bug#44313)
> > > > >
> > > > > Yes, according to "git branch --contains" the commit is present. The
> > > > > exception report makes me think that NSApp is null or invalid, but how
> > > > > should that be possible?
> > > >
> > > > I have no idea... What's happening when the crash occurs? I take it
> > > > the mouse is being moved, but are frames opening and closing or
> > > > anything?
> > >
> > > I'm now able to reproduce this consistently. It happens when a tooltip
> > > appears and you hover over that tooltip (try M-x locate and move the
> > > mouse around).
> > > The crash is in the line
> > > if (f && FRAME_NS_P (f))
> > > in nsterm.m in ns_mouse_position, so apparently "f" is not NULL, but
> > > also not valid.
> >
> > Looks like "f" isn't initialized to NULL in that function?
>
> This was probably fixed with commit
> b4911a6f0da0bfae3832b3aa0c111db4bb2f49d5 on master. I guess we should
> backport the one-line initialization change onto the release branch,
> since the crash is nasty and the fix is trivial.
Yes, I agree.
--
Alan Third
next prev parent reply other threads:[~2020-12-30 15:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-29 22:32 bug#45541: 28.0.50; Frequent crashes on ARM macOS Philipp
2020-12-30 0:10 ` Alan Third
2020-12-30 13:01 ` Philipp Stephani
2020-12-30 14:05 ` Alan Third
2020-12-30 14:42 ` Philipp Stephani
2020-12-30 14:49 ` Philipp Stephani
2020-12-30 14:53 ` Philipp Stephani
2020-12-30 15:22 ` Alan Third [this message]
2021-01-01 10:40 ` Alan Third
2021-01-01 11:21 ` Philipp Stephani
2020-12-30 20:35 ` Eli Zaretskii
2020-12-30 21:10 ` Philipp Stephani
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=X+ybOEjxGVomdFGM@breton.holly.idiocy.org \
--to=alan@idiocy.org \
--cc=45541@debbugs.gnu.org \
--cc=p.stephani2@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).