all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Noam Postavsky <npostavs@gmail.com>,martin rudalics <rudalics@gmx.at>
Cc: 35784@debbugs.gnu.org, marc@bloodnok.com
Subject: bug#35784: emacs 26 crash
Date: Sun, 19 May 2019 07:51:21 +0300	[thread overview]
Message-ID: <2A54F0AC-6D10-45CA-B0BD-DA3D445FF96C@gnu.org> (raw)
In-Reply-To: <87ftpbcfwc.fsf@gmail.com>

On May 19, 2019 5:54:59 AM GMT+03:00, Noam Postavsky <npostavs@gmail.com> wrote:
> >>> #2  0x000000000061849e in die (msg=0x743f3f "BUFFERP (a)",
> >>> file=0x743f36 "buffer.h", line=914) at alloc.c:7406
> >>> #3  0x00000000005802b3 in XBUFFER (a=0) at buffer.h:914
> >>> #4  0x0000000000468bb3 in mark_window_display_accurate_1
> (w=0x558e410,
> >>> accurate_p=false) at xdisp.c:14754
> >>>          b = 0x7ffe74b60e40
> >>> #5  0x0000000000468ffd in mark_window_display_accurate
> >>> (window=89711637, accurate_p=false) at xdisp.c:14811
> >>>          w = 0x558e410
> >>> #6  0x00000000004bbe06 in Fforce_window_update (object=89711637)
> at
> >>> window.c:3643
> >>>          w = 0x558e410
> >>
> >> This seems to imply that we are trying to update a non-leaf window,
> >> something that should never happen.  There's no Lisp-level
> backtrace,
> >> so it's hard to tell what Lisp called force-window-update, and how
> the
> >> window in question became non-leaf, but maybe some crazy Lisp hook
> >> switched windows behind redisplay's back or something.
> >
> > I'd rather guess that this is the result of 'kill-buffer' called
> from
> > 'delete-frame-functions' or 'delete-frame' called from
> > 'kill-buffer-hook'.  But at the moment I can't reproduce the bug
> here
> > any more.
> 
> The Lisp backtrace is:
> 
> "force-window-update" (0xffffd640)
> 0x2f61c80 Lisp type 3
> "mapc" (0xffffd960)
> "k-tabbar2::pc-handle-queued-updates" (0xffffdb00)
> "k-tabbar2::post-command-fn" (0xffffddf0)
> 
> I think the problem is just that the Lisp code is calling
> force-window-update on a deleted window.  At least, I can trigger the
> crash with
> 
>     (let ((w (split-window)))
>       (delete-window w)
>       (force-window-update w))
> 
> And the following fixes it:
> 
> --- i/src/window.c
> +++ w/src/window.c
> @@ -4089,7 +4089,7 @@ displaying that buffer.  */)
>        return Qt;
>      }
>  
> -  if (WINDOWP (object))
> +  if (WINDOW_LIVE_P (object))
>      {
>        struct window *w = XWINDOW (object);
>        mark_window_display_accurate (object, false);

Thanks, this fix is fine with me.  Martin?





  reply	other threads:[~2019-05-19  4:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-17 20:54 bug#35784: emacs 26 crash Marc Munro
2019-05-18  6:19 ` Eli Zaretskii
2019-05-18  9:39   ` Bhavin Gandhi
2019-05-18 12:09     ` Eli Zaretskii
2019-05-18 12:16   ` Noam Postavsky
2019-05-18 13:03     ` Eli Zaretskii
2019-05-18 14:03     ` martin rudalics
2019-05-18 14:19       ` Noam Postavsky
2019-05-18 15:39         ` Eli Zaretskii
2019-05-18 17:30           ` martin rudalics
2019-05-18 17:43             ` Eli Zaretskii
2019-05-19  2:54             ` Noam Postavsky
2019-05-19  4:51               ` Eli Zaretskii [this message]
2019-05-19  6:40                 ` martin rudalics
2019-05-19 17:11                   ` Noam Postavsky
2019-05-19 17:59                     ` Eli Zaretskii
2019-05-20 18:27                       ` Noam Postavsky
2019-05-19 23:57 ` bug#35784: Just built from head: it seems to be fixed Marc Munro

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=2A54F0AC-6D10-45CA-B0BD-DA3D445FF96C@gnu.org \
    --to=eliz@gnu.org \
    --cc=35784@debbugs.gnu.org \
    --cc=marc@bloodnok.com \
    --cc=npostavs@gmail.com \
    --cc=rudalics@gmx.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.