GNU bug report logs - #35784
(force-window-update <DELETED-WINDOW>) segfaults

Previous Next

Package: emacs;

Reported by: Marc Munro <marc <at> bloodnok.com>

Date: Fri, 17 May 2019 21:07:02 UTC

Severity: normal

Tags: fixed, patch

Fixed in version 26.3

Done: Noam Postavsky <npostavs <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


Message #35 received at 35784 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: martin rudalics <rudalics <at> gmx.at>
Cc: 35784 <at> debbugs.gnu.org, npostavs <at> gmail.com, marc <at> bloodnok.com
Subject: Re: bug#35784: emacs 26 crash
Date: Sat, 18 May 2019 20:43:09 +0300
> Cc: 35784 <at> debbugs.gnu.org, marc <at> bloodnok.com
> From: martin rudalics <rudalics <at> gmx.at>
> Date: Sat, 18 May 2019 19:30:50 +0200
> 
>  > 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'.

kill-buffer is supposed to replace the killed buffer with another in
all windows, so we shouldn't end up with a window's buffer being nil.
But I'm louse at guessing causes for problems just by looking at them,
so you may be right.




This bug report was last modified 6 years and 86 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.