From: Tobias Bading <tbading@web.de>
To: 63312@debbugs.gnu.org
Cc: Eli Zaretskii <eliz@gnu.org>
Subject: bug#63312: 29.0.90; set-frame-parameter sometimes called with dead frame when quitting ediff
Date: Sat, 6 May 2023 09:27:35 +0200 [thread overview]
Message-ID: <bd1e495a-44c8-5d0d-3eb2-8264993fa8ee@web.de> (raw)
In-Reply-To: <83zg6ihdlz.fsf@gnu.org>
> Can you set debug-on-error non-nil, and post the full Lisp backtrace
> from the error?
Just now I couldn’t reproduce the bug in my tweaked Emacs 29. After a
sudo cpupower frequency-set --max 400MHz
I could. In my clean build of emacs-29 branch 21ec6c1d5c I was able to
reproduce the bug without any CPU throttling. The result is the same:
Debugger entered--Lisp error: (wrong-type-argument frame-live-p #<dead frame Ediff 0x55e8aa9e3760>)
modify-frame-parameters(#<dead frame Ediff 0x55e8aa9e3760> ((dnd-root-window-position)))
set-frame-parameter(#<dead frame Ediff 0x55e8aa9e3760> dnd-root-window-position nil)
x-dnd-after-move-frame(#<dead frame Ediff 0x55e8aa9e3760>)
run-hook-with-args(x-dnd-after-move-frame #<dead frame Ediff 0x55e8aa9e3760>)
handle-move-frame((move-frame (#<dead frame Ediff 0x55e8aa9e3760>)))
funcall-interactively(handle-move-frame (move-frame (#<dead frame Ediff 0x55e8aa9e3760>)))
call-interactively(handle-move-frame nil [(move-frame (#<dead frame Ediff 0x55e8aa9e3760>))])
command-execute(handle-move-frame nil [(move-frame (#<dead frame Ediff 0x55e8aa9e3760>))] t)
next prev parent reply other threads:[~2023-05-06 7:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 17:02 bug#63312: 29.0.90; set-frame-parameter sometimes called with dead frame when quitting ediff Tobias Bading
2023-05-05 17:50 ` Eli Zaretskii
2023-05-06 7:27 ` Tobias Bading [this message]
2023-05-06 9:42 ` Eli Zaretskii
2023-05-06 10:10 ` Tobias Bading
2023-05-06 10:34 ` Eli Zaretskii
2023-05-06 11:12 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-06 11:17 ` Eli Zaretskii
2023-05-06 12:01 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=bd1e495a-44c8-5d0d-3eb2-8264993fa8ee@web.de \
--to=tbading@web.de \
--cc=63312@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).