From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Clemente <n142857@gmail.com>
Cc: 71289@debbugs.gnu.org
Subject: bug#71289: 30.0.50; cmcheckmagic aborts when tty_write_glyphs writes "Garbage collecting..." in some cases
Date: Fri, 31 May 2024 21:26:41 +0300 [thread overview]
Message-ID: <86bk4lq1lq.fsf@gnu.org> (raw)
In-Reply-To: <CAJKAhPC-Xip3gm6WFSdamY09b9O-1h4yeqKSRQaUYk-MceDCUA@mail.gmail.com> (message from Daniel Clemente on Fri, 31 May 2024 17:09:29 +0000)
> From: Daniel Clemente <n142857@gmail.com>
> Date: Fri, 31 May 2024 17:09:29 +0000
> Cc: Eli Zaretskii <eliz@gnu.org>
>
> While playing with resizing the urxvt terminal size (X window), I
> found other bugs where Emacs doesn't know the real size of the
> terminal, or becomes unsynchronized with the actual terminal size.
> This may cause many of the other bugs I've seen (things in the style
> of: the GC message wants to use 2 minibuffer lines because it thinks
> there are 2 lines, but actually there's just 1, etc.).
>
> The two resizing bugs I found (but I don't have time to research them
> in detail yet) are:
> - if the X terminal has 4 visible rows, FrameRows(tty) reports 4. If
> 3, then 3. But if it has 2 or 1 rows, Emacs still sees 3. And editing
> is garbled
> - if I decrease the terminal size fast, e.g. 81→71→61→51→41→31→21→11→1
> lines, often Emacs doesn't notice all changes, and it may still report
> that FrameRows(tty) is e.g. 31 when it went further down to 1
> (31→21→11→1)
>
> - in addition there's a more complex refresh bug (not about resizing I
> think), in which the next frame I focus after having killed a frame
> won't be refreshed (e.g. I can resize the X window and it doesn't
> notice, new sections appear black) until I press a key or move the
> mouse. It's 100% reproducible but I need to research this better
> because it involves window managers and X
>
> However I didn't see a direct crash from these issues. But maybe a GC
> message in some of these conditions can cause the alert.
>
> I may report them as separate bugs but in a while; I'm reporting too
> many TTY bugs and too fast; I need time for other things.
>
> I also saw a new type of TTY+GC error (not sure if it's the same issue
> as this bug):
Please investigate what happens with our SIGWINCH handler (in
dispnew.c) in these cases.
next prev parent reply other threads:[~2024-05-31 18:26 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 10:18 bug#71289: 30.0.50; cmcheckmagic aborts when tty_write_glyphs writes "Garbage collecting..." in some cases Daniel Clemente
2024-05-31 11:17 ` Eli Zaretskii
2024-05-31 17:07 ` Daniel Clemente
2024-05-31 18:17 ` Eli Zaretskii
2024-06-03 15:35 ` Daniel Clemente
2024-06-03 16:21 ` Eli Zaretskii
2024-05-31 17:09 ` Daniel Clemente
2024-05-31 18:26 ` Eli Zaretskii [this message]
2024-06-03 15:56 ` Daniel Clemente
2024-06-03 16:03 ` Eli Zaretskii
2024-06-03 16:28 ` Daniel Clemente
2024-06-03 16:36 ` Eli Zaretskii
2024-06-03 16:51 ` Daniel Clemente
2024-06-03 17:44 ` Eli Zaretskii
2024-06-05 13:51 ` Daniel Clemente
2024-06-06 7:55 ` Eli Zaretskii
2024-06-03 15:36 ` Daniel Clemente
2024-06-03 16:25 ` Eli Zaretskii
2024-06-03 16:55 ` Daniel Clemente
2024-06-03 17:39 ` Eli Zaretskii
2024-06-05 13:50 ` Daniel Clemente
2024-06-05 15:06 ` Eli Zaretskii
2024-06-05 16:43 ` Eli Zaretskii
2024-06-06 12:36 ` Daniel Clemente
2024-06-06 12:34 ` Daniel Clemente
2024-06-06 14:53 ` Eli Zaretskii
2024-06-06 15:23 ` Daniel Clemente
2024-06-06 16:13 ` Eli Zaretskii
2024-06-06 16:44 ` Daniel Clemente
2024-06-06 18:06 ` Daniel Clemente
2024-06-07 6:11 ` Eli Zaretskii
2024-06-07 6:42 ` Daniel Clemente
2024-06-07 6:47 ` Eli Zaretskii
2024-06-05 13:52 ` Daniel Clemente
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=86bk4lq1lq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=71289@debbugs.gnu.org \
--cc=n142857@gmail.com \
/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).