From: Alan Third <alan@idiocy.org>
To: John Mastro <john.b.mastro@gmail.com>
Cc: 28661@debbugs.gnu.org, Kevin Lin <lin.kevin.k@gmail.com>
Subject: bug#28661: 25.3; closing fullscreen frame on macOS 10.13 High Sierra causes crash
Date: Mon, 2 Oct 2017 23:34:17 +0100 [thread overview]
Message-ID: <20171002223417.GA50504@breton.holly.idiocy.org> (raw)
In-Reply-To: <CAOj2CQRjN4CDPKHTy2rihm_fwMGKQbFeaFedii2+3QoB6UbLcw@mail.gmail.com>
On Mon, Oct 02, 2017 at 02:27:51PM -0700, John Mastro wrote:
> Sure, I've attached a backtrace from lldb. Let me know if any other
> info would help.
Thank you.
> frame #0: 0x00000001001b629d Emacs`-[EmacsView windowWillResize:toSize:](self=0x000000010c33a700, _cmd=<unavailable>, sender=<unavailable>, frameSize=(width = 1280, height = 800)) at nsterm.m:6912 [opt]
> 6909
> 6910 if (! [self isFullscreen])
> 6911 {
> -> 6912 extra = FRAME_NS_TITLEBAR_HEIGHT (emacsframe)
> 6913 + FRAME_TOOLBAR_HEIGHT (emacsframe);
> 6914 }
Well, that’s just about the last thing I was expecting.
I guess that closing a fullscreen window now results in it being
resized. But is emacsframe already trashed by this point? That would
certainly cause a crash.
Can you please uncomment line 54 in nsterm.h to enable NSTRACE,
recompile, cause the crash and send the output to me?
--
Alan Third
next prev parent reply other threads:[~2017-10-02 22:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-01 15:43 bug#28661: 25.3; closing fullscreen frame on macOS 10.13 High Sierra causes crash Kevin Lin
2017-10-01 19:33 ` Alan Third
2017-10-01 22:07 ` Kevin Lin
2017-10-01 22:56 ` John Mastro
2017-10-01 23:01 ` Alan Third
2017-10-02 21:27 ` John Mastro
2017-10-02 22:34 ` Alan Third [this message]
2017-10-05 0:44 ` John Mastro
2017-10-07 15:08 ` Alan Third
2017-10-07 17:46 ` John Mastro
2017-10-07 20:56 ` Alan Third
2017-10-07 22:50 ` Kevin Lin
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=20171002223417.GA50504@breton.holly.idiocy.org \
--to=alan@idiocy.org \
--cc=28661@debbugs.gnu.org \
--cc=john.b.mastro@gmail.com \
--cc=lin.kevin.k@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).