From: Alan Third <alan@idiocy.org>
To: David Reitter <david.reitter@gmail.com>,
Matthew Bauer <mjbauer95@gmail.com>,
emacs-devel@gnu.org
Subject: Re: bug#26323: 25.1; Closing frames (in fullscreen) under Mac OS cause immediate crash
Date: Sun, 18 Mar 2018 20:14:16 +0000 [thread overview]
Message-ID: <20180318201416.GA7641@breton.holly.idiocy.org> (raw)
In-Reply-To: <m2o9jlxndf.fsf@newartisans.com>
On Sun, Mar 18, 2018 at 11:14:04AM -0700, John Wiegley wrote:
> >>>>> "DR" == David Reitter <david.reitter@gmail.com> writes:
>
> DR> On Mar 18, 2018, at 7:15 AM, Alan Third <alan@idiocy.org> wrote:
> >>> It reproduced in a mid-2016 build, and in a current build (based on the 25
> >>> branch).
> >>
> >> It was fixed after that. I can’t reproduce it in Emacs 26.
>
> DR> Is this going to be backported to 25?
>
> When was this fixed? It happens to me in Emacs 26 every time.
I haven’t been able to replicate it since sometime around the middle
of last year. Additionally there was a fix for macOS 10.13 installed
in emacs-26 in October last year.
I still can’t replicate it.
If anyone is able to provide a backtrace for either emacs 26 or the
master branch crashing, that would be helpful.
--
Alan Third
next prev parent reply other threads:[~2018-03-18 20:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 0:54 bug#26323: 25.1; Closing frames (in fullscreen) under Mac OS cause immediate crash Matthew Bauer
2018-03-16 10:47 ` Alan Third
2018-03-16 18:12 ` David Reitter
2018-03-18 11:15 ` Alan Third
2018-03-18 11:17 ` David Reitter
2018-03-18 11:30 ` Alan Third
2018-03-18 18:14 ` John Wiegley
2018-03-18 20:14 ` Alan Third [this message]
2018-03-19 0:37 ` Nick Helm
2018-03-19 12:29 ` Alan Third
2018-03-19 2:05 ` Matthew Bauer
2018-03-19 12:23 ` Alan Third
2018-03-20 1:05 ` John Wiegley
-- strict thread matches above, loose matches on Subject: below --
2018-07-10 20:52 Noah Sussman
2018-07-12 20:51 ` Alan Third
2018-07-13 2:16 ` Radon Rosborough
2018-07-13 20:25 ` Noah Sussman
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=20180318201416.GA7641@breton.holly.idiocy.org \
--to=alan@idiocy.org \
--cc=david.reitter@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=mjbauer95@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).