From: Eli Zaretskii <eliz@gnu.org>
To: Aaron Jensen <aaronjensen@gmail.com>
Cc: alan@idiocy.org, 30800@debbugs.gnu.org
Subject: bug#30800: 26.0.91; unknown crash on macos
Date: Thu, 22 Mar 2018 17:57:56 +0200 [thread overview]
Message-ID: <83po3whzln.fsf@gnu.org> (raw)
In-Reply-To: <CAHyO48zrXe_OXiq0mB=gZqkXqgw7FTv=OP-jDEvFumhRuWzZtg@mail.gmail.com> (message from Aaron Jensen on Thu, 22 Mar 2018 08:39:32 -0700)
> From: Aaron Jensen <aaronjensen@gmail.com>
> Date: Thu, 22 Mar 2018 08:39:32 -0700
> Cc: Alan Third <alan@idiocy.org>, 30800@debbugs.gnu.org
>
> > Do you still see the flicker if you revert the above commit?
>
> I do not on 10.13.2 when I follow the steps outlined in the original report.
>
> I don't know what's going on in the code exactly, but would it be
> worth it to risk the flicker on older macOS (or people's setups that
> can repro it if mine just can't) in order to ensure that the
> represented filename gets set on a frame that is about to be freed?
I don't know. I leave it to you, users of macOS, to make that
decision. Perhaps the patch you are trying is indeed the best fix
(assuming it works), given that the problem is less likely to happen
now.
next prev parent reply other threads:[~2018-03-22 15:57 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 16:18 bug#30800: 26.0.91; unknown crash on macos Aaron Jensen
2018-03-13 16:36 ` Aaron Jensen
2018-03-20 23:39 ` Aaron Jensen
2018-03-21 6:37 ` Eli Zaretskii
2018-03-21 16:25 ` Aaron Jensen
2018-03-21 17:00 ` Eli Zaretskii
2018-03-21 17:09 ` Eli Zaretskii
2018-03-21 17:31 ` Aaron Jensen
2018-03-21 18:22 ` Eli Zaretskii
2018-03-21 18:31 ` Aaron Jensen
2018-03-21 18:48 ` Eli Zaretskii
2018-03-21 19:19 ` Alan Third
2018-03-21 19:36 ` Eli Zaretskii
2018-03-21 20:12 ` Alan Third
2018-03-22 5:40 ` Aaron Jensen
2018-03-22 7:26 ` Eli Zaretskii
2018-03-22 15:39 ` Aaron Jensen
2018-03-22 15:57 ` Eli Zaretskii [this message]
2018-03-23 1:49 ` Aaron Jensen
2018-03-23 8:16 ` Eli Zaretskii
2018-03-23 19:52 ` Alan Third
2018-03-23 20:57 ` Aaron Jensen
2018-03-24 7:20 ` Aaron Jensen
2018-03-24 10:29 ` Alan Third
2018-03-24 14:54 ` Eli Zaretskii
2018-03-24 16:18 ` Alan Third
2018-03-24 17:48 ` Eli Zaretskii
2018-03-25 19:17 ` Alan Third
2018-03-24 10:49 ` Charles A. Roelli
2018-03-24 14:12 ` Alan Third
2018-03-25 20:14 ` Charles A. Roelli
2018-03-26 18:37 ` Alan Third
2018-03-26 23:03 ` Aaron Jensen
2018-03-30 11:37 ` Alan Third
2018-03-30 11:57 ` Aaron Jensen
2018-03-22 5:35 ` Aaron Jensen
2018-03-22 7:16 ` Eli Zaretskii
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=83po3whzln.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=30800@debbugs.gnu.org \
--cc=aaronjensen@gmail.com \
--cc=alan@idiocy.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).