From: Alan Third <alan@idiocy.org>
To: David Reitter <david.reitter@gmail.com>
Cc: 24581@debbugs.gnu.org, konrad podczeck <konrad.podczeck@univie.ac.at>
Subject: bug#24581: 25.1 crash in ns_scroll_run after closing a frame
Date: Sat, 1 Oct 2016 21:35:03 +0100 [thread overview]
Message-ID: <20161001203503.GA39868@breton.holly.idiocy.org> (raw)
In-Reply-To: <39492EB9-84DE-49A4-84BD-E48A31BE9492@gmail.com>
On Sat, Oct 01, 2016 at 10:17:24AM -0400, David Reitter wrote:
> X-Debbugs-CC: Konrad Podczeck <konrad.podczeck@univie.ac.at>
> This is with our latest build, which is derived from the Emacs 25 branch.
>
> Is it possible that we’re trying to redisplay or scroll after the window was removed?
> The stack trace might be actionable in this case, so I’m reporting this here.
I’m inclined to suspect that we’re processing input while the OS is
closing the frame. We got similar crashes when minimizing without
blocking input.
> > 21 org.gnu.Aquamacs 0x0000000100005907 update_frame + 135
> > 22 org.gnu.Aquamacs 0x0000000100029563 redisplay_internal + 6083
> > 23 org.gnu.Aquamacs 0x00000001000ca4af read_char + 1999
^^^^^^^^^
> > 24 org.gnu.Aquamacs 0x00000001000c7bfa read_key_sequence + 1946
> > 25 org.gnu.Aquamacs 0x00000001000c6332 command_loop_1 + 1154
> > 26 org.gnu.Aquamacs 0x0000000100145349 internal_condition_case + 265
Unfortunately it looks like input is already blocked when closing the
frame (nsterm.m:1657), so I’m a little at a loss.
(I’m assuming that by ‘after closing a frame’ you mean as soon as you
close it, and not that there’s a pause then the crash?)
Is it possible to recompile with NSTRACE turned on so we can see the
sequence of NS functions up to a crash?
--
Alan Third
next prev parent reply other threads:[~2016-10-01 20:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5457C3AC-EEBA-403F-B27D-6C78F59F9F4A@univie.ac.at>
2016-10-01 14:17 ` bug#24581: 25.1 crash in ns_scroll_run after closing a frame David Reitter
2016-10-01 15:56 ` Eli Zaretskii
2016-10-01 20:35 ` Alan Third [this message]
2016-10-03 1:55 ` David Reitter
[not found] ` <CABGBtwmdW+hJRYBHtqH0mRspBadPGpGqoCAcndrFChYGJbMoKw@mail.gmail.com>
2016-10-03 6:59 ` Alan Third
2020-08-12 1:17 ` Stefan Kangas
2020-08-12 10:22 ` David Reitter
2020-08-13 18:21 ` Win Treese
2020-08-13 18:46 ` Alan Third
2020-08-13 20:51 ` Win Treese
2020-08-14 9:51 ` Robert Pluim
2020-08-14 14:43 ` Win Treese
2020-08-14 20:06 ` Alan Third
2020-08-14 19:58 ` Alan Third
2020-10-10 9:45 ` Alan Third
2020-10-10 16:23 ` Win Treese
2020-10-10 16:26 ` Stefan Kangas
2020-10-11 8:44 ` Alan Third
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161001203503.GA39868@breton.holly.idiocy.org \
--to=alan@idiocy.org \
--cc=24581@debbugs.gnu.org \
--cc=david.reitter@gmail.com \
--cc=konrad.podczeck@univie.ac.at \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.