unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Tassilo Horn <tsdh@gnu.org>
To: Arash Esbati <arash@gnu.org>
Cc: 53871@debbugs.gnu.org
Subject: bug#53871: 29.0.50; Emacs freezes with new child-frame option
Date: Tue, 08 Feb 2022 11:35:17 +0100	[thread overview]
Message-ID: <87pmnxy7bu.fsf@gnu.org> (raw)
In-Reply-To: <86leylvjf5.fsf@gnu.org> (Arash Esbati's message of "Tue, 08 Feb 2022 09:42:22 +0100")

Arash Esbati <arash@gnu.org> writes:

Hi Arash,

> I'm trying the new option child-frame available for
> `show-paren-context-when-offscreen' (introduced in 6e5d79c048) and I'm
> running into an issue where Emacs freezes.  Steps to trigger:
>
> 1) emacs -Q
> 2) eval (setq show-paren-context-when-offscreen t) in scratch
> 3) M-x find-library RET paren RET
> 4) M-g c 13902 RET
> 5) With the mouse cursor, grab the scroll bar and move down so far to
>    get the context
>    'Matches (defun show-paren--show-context-in-child-frame (text)'
>    in the echo area.
> 6) eval (setq show-paren-context-when-offscreen 'child-frame) in scratch
> 7) Repeat 5) and Emacs freezes
>
> This is with repo-version 90eb6a7fe4 on Win10.

I can't reproduce with the slightly later version 9d1ae05442 on
GNU/Linux with a pgtk build.  When scroll up and down (only so far as to
keep point at the closing paren of the defun), I'll see the child frame
displaying the "(defun ...)" line whenever I stop scrolling for a
second.

After doing that for I while, I checked that `(frame-list)` still
contains just a single frame.  How is that for you?  Do you have many
frames in there?  And do you recover from the freeze?

Does doing the recipe with debug-on-quit set and then doing C-g when the
freeze occurs shed some light?

Bye,
Tassilo





  reply	other threads:[~2022-02-08 10:35 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 [this message]
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
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

  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=87pmnxy7bu.fsf@gnu.org \
    --to=tsdh@gnu.org \
    --cc=53871@debbugs.gnu.org \
    --cc=arash@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).