From: Marius Kjeldahl <marius.kjeldahl@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, John Wiegley <jwiegley@gmail.com>
Cc: alan@idiocy.org, emacs-devel@gnu.org
Subject: Re: Bug#23924 - crashes on next OS X release
Date: Wed, 03 Aug 2016 07:07:49 +0000 [thread overview]
Message-ID: <CAHdMyCJ5sht1Y_bMzoki04DK9D-W6CwDGQS76dt7iNfdGTJa9g@mail.gmail.com> (raw)
In-Reply-To: <83a8gumvbr.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1414 bytes --]
Well, I'm one of the testers I guess. I spend more or less all day with
Emacs, and before applying the patch I had several crashes a day, and after
zero. However, it's a hard bug to pin down (some kind of timing/racing
condition I suspect). Accordingly there is no simple test case that can be
applied that I am aware of. Based on the short time between the last two
macOS beta releases (3 and 4) and the fact that the last version barely had
any "change notes", I suspect macOS release is getting close. I would feel
a lot more comfortable if all modern distributions of Emacs on macOS had
this patch in rather than not. When/if we manage to pin it down with a
reliable test case, a real fix of this or the underlying issue should be
easier, but until then I vote to get the patch in ASAP. Additionally the
patch only affects macOS users so the breakage potential should be small
(at least compared to daily crashes which is the alternative).
On Wed, 3 Aug 2016 at 04:39 Eli Zaretskii <eliz@gnu.org> wrote:
> > From: John Wiegley <jwiegley@gmail.com>
> > Cc: Eli Zaretskii <eliz@gnu.org>, Emacs-Devel devel <
> emacs-devel@gnu.org>
> > Date: Tue, 02 Aug 2016 13:25:10 -0700
> >
> > >>>>> Alan Third <alan@idiocy.org> writes:
> >
> > > Hi John, are you OK with the patch?
> >
> > Yes, I am OK with the patch. Eli?
>
> If all those affected by the problem agree it's TRT, I'm OK with it
> going to emacs-25.
>
>
[-- Attachment #2: Type: text/html, Size: 1996 bytes --]
next prev parent reply other threads:[~2016-08-03 7:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 14:02 Bug#23924 - crashes on next OS X release Alan Third
2016-07-18 14:49 ` Eli Zaretskii
2016-07-18 16:16 ` John Wiegley
2016-07-18 19:03 ` Alan Third
2016-07-19 23:28 ` David Caldwell
2016-07-22 21:54 ` Alan Third
2016-08-02 14:59 ` Alan Third
2016-08-02 20:25 ` John Wiegley
2016-08-03 2:37 ` Eli Zaretskii
2016-08-03 7:07 ` Marius Kjeldahl [this message]
2016-08-03 8:39 ` Alan Third
2016-08-03 16:57 ` Alan Third
2016-08-03 19:50 ` Nicolas Petton
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=CAHdMyCJ5sht1Y_bMzoki04DK9D-W6CwDGQS76dt7iNfdGTJa9g@mail.gmail.com \
--to=marius.kjeldahl@gmail.com \
--cc=alan@idiocy.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jwiegley@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).