From: Philipp Stephani <p.stephani2@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Alan Third <alan@idiocy.org>, 45541@debbugs.gnu.org
Subject: bug#45541: 28.0.50; Frequent crashes on ARM macOS
Date: Wed, 30 Dec 2020 22:10:16 +0100 [thread overview]
Message-ID: <CAArVCkQ=uLUM-qiyZWhH0Ag-Bg2ty8mGbrvJqHT814T3wVz0Mw@mail.gmail.com> (raw)
In-Reply-To: <83ft3nhw1g.fsf@gnu.org>
Am Mi., 30. Dez. 2020 um 21:35 Uhr schrieb Eli Zaretskii <eliz@gnu.org>:
>
> > From: Philipp Stephani <p.stephani2@gmail.com>
> > Date: Wed, 30 Dec 2020 15:42:24 +0100
> >
> > I'm now able to reproduce this consistently. It happens when a tooltip
> > appears and you hover over that tooltip
>
> How is that possible? Tooltips are supposed to pop down as soon as
> you move the mouse. Are those native NS tooltips, and if so, do they
> behave differently in this regard?
Yes, they don't vanish immediately when hovering over them.
>
> > 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.
>
> Maybe, if the tooltip popped down, we need to test whether f is a live
> frame?
We need to initialize "f" to NULL, because the loop that sets it
doesn't necessarily find a frame.
prev parent reply other threads:[~2020-12-30 21:10 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
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 [this message]
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='CAArVCkQ=uLUM-qiyZWhH0Ag-Bg2ty8mGbrvJqHT814T3wVz0Mw@mail.gmail.com' \
--to=p.stephani2@gmail.com \
--cc=45541@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=eliz@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).