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 13:09:38 +0100 [thread overview]
Message-ID: <87h799y2cd.fsf@gnu.org> (raw)
In-Reply-To: <86y22lwojc.fsf@gnu.org>
Arash Esbati <arash@gnu.org> writes:
>> After doing that for I while, I checked that `(frame-list)` still
>> contains just a single frame. How is that for you?
>
> Thanks for your response. It is the same, only one frame.
Hm, `frame-list' says it doesn't return "tooltip frames". I think
that's something else than child frames but you might try
`(frames-on-display-list)', too. It should also return a single frame
unless a show-paren child-frame is still visible.
>> And do you recover from the freeze?
>
> No recovery, Emacs freezes hard and I have to kill it from the shell.
Could you get a backtrace with GDB? Basically just
$ gdb src/emacs -x src/.gdbinit
> run
# do your scroll stuff until it freezes and then hit C-z in gdb and do
> xbacktrace # get a lisp backtrace
> bt full # get a C backtrace
The C backtrace is probably large so please compress is before attaching
it here.
>> Does doing the recipe with debug-on-quit set and then doing C-g when
>> the freeze occurs shed some light?
>
> See above. Interesting point is that scrolling with mouse wheel isn't
> a problem, things play havoc if I touch the scroll bar with the mouse
> pointer.
Could you put a message in show-paren--show-context-in-child-frame just
to get a feeling of how often a child frame is created?
Bye,
Tassilo
next prev parent reply other threads:[~2022-02-08 12:09 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 [this message]
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=87h799y2cd.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).