all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: arash@gnu.org, tsdh@gnu.org, 53871@debbugs.gnu.org
Subject: bug#53871: 29.0.50; Emacs freezes with new child-frame option
Date: Tue, 08 Feb 2022 20:55:55 +0200	[thread overview]
Message-ID: <837da5w5l0.fsf@gnu.org> (raw)
In-Reply-To: <9c60c76c-4061-907b-7206-66b6fe3a6491@gmx.at> (message from martin rudalics on Tue, 8 Feb 2022 19:23:21 +0100)

> Date: Tue, 8 Feb 2022 19:23:21 +0100
> Cc: arash@gnu.org, 53871@debbugs.gnu.org
> From: martin rudalics <rudalics@gmx.at>
> 
>  > Martin, any ideas?  I can show the backtrace from the freeze, if that
>  > helps.
> 
> No ideas.  I also observed that the scroll bar in the main frame must be
> involved.  Mouse-wheel scrolling doesn't freeze it here either.  So we
> seem to have two competing windows - the scroll bar window and the child
> frame window - which we would have to disentangle somehow.

How come we don't see something similar in any other code that creates
child frames?  Scrolling via the scroll bars is possible while some
Lisp creates child frames not necessarily in this context.  Are our
frame creation so fragile that it doesn't tolerate scroll bars in
parallel with frame creation?





  reply	other threads:[~2022-02-08 18:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-08  8:42 bug#53871: 29.0.50; Emacs freezes with new child-frame option Arash Esbati
2022-02-08 10:35 ` Tassilo Horn
2022-02-08 12:06   ` Arash Esbati
2022-02-08 12:09     ` Tassilo Horn
2022-02-08 15:09   ` Eli Zaretskii
2022-02-08 18:23     ` martin rudalics
2022-02-08 18:55       ` Eli Zaretskii [this message]
2022-02-09  0:41         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-09  3:33           ` Eli Zaretskii

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=837da5w5l0.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=53871@debbugs.gnu.org \
    --cc=arash@gnu.org \
    --cc=rudalics@gmx.at \
    --cc=tsdh@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 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.