From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Daniel Clemente Newsgroups: gmane.emacs.bugs Subject: bug#71289: 30.0.50; cmcheckmagic aborts when tty_write_glyphs writes "Garbage collecting..." in some cases Date: Mon, 3 Jun 2024 15:56:17 +0000 Message-ID: References: <86bk4lq1lq.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="00000000000059749c0619fe615d" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="35461"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 71289@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Jun 03 17:59:16 2024 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1sEA5b-000913-M5 for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 03 Jun 2024 17:59:15 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1sEA5D-0001yT-AJ; Mon, 03 Jun 2024 11:58:51 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1sEA5B-0001wI-Cg for bug-gnu-emacs@gnu.org; Mon, 03 Jun 2024 11:58:49 -0400 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1sEA5B-00069E-5B for bug-gnu-emacs@gnu.org; Mon, 03 Jun 2024 11:58:49 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1sEA5N-0000n3-Om for bug-gnu-emacs@gnu.org; Mon, 03 Jun 2024 11:59:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Daniel Clemente Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 03 Jun 2024 15:59:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 71289 X-GNU-PR-Package: emacs Original-Received: via spool by 71289-submit@debbugs.gnu.org id=B71289.17174302872884 (code B ref 71289); Mon, 03 Jun 2024 15:59:01 +0000 Original-Received: (at 71289) by debbugs.gnu.org; 3 Jun 2024 15:58:07 +0000 Original-Received: from localhost ([127.0.0.1]:45349 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1sEA4U-0000kR-Rx for submit@debbugs.gnu.org; Mon, 03 Jun 2024 11:58:07 -0400 Original-Received: from mail-ua1-f44.google.com ([209.85.222.44]:61522) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1sEA4S-0000jk-O4 for 71289@debbugs.gnu.org; Mon, 03 Jun 2024 11:58:05 -0400 Original-Received: by mail-ua1-f44.google.com with SMTP id a1e0cc1a2514c-80ac8c7caddso1324931241.2 for <71289@debbugs.gnu.org>; Mon, 03 Jun 2024 08:57:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1717430206; x=1718035006; darn=debbugs.gnu.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=0HOFtv9+hTvv/BrBRPyVlEYG3mY3IG/M5dOr58sRYAc=; b=GPZbukuBMj48xqimc2dQLINxp09owNbVr4ZXn86wmwILOxDlYViRymgUZdUeY8+a1F mglkqziYFSq6kkJWMSS+Rq2xebwaM6gNS55y+LBJ1EFKLfUOl5yJZos0W1E+15IcZ4eL vfDxSGl9x78OF+cg/emCSapZszI5xDHkQS5Ygn/T69+hQpODqH7gP+vY2jooV0GllUzF xTHaNGcNmGxKR7xRQnhFsQgJH1N7guLywLmrYwQAPBRr4/fOeabuuBv0A4fxQANd77m1 L/ZIEkXsAw0BKmf2VeSWcx80hteXA+vHjPIOM+nN6IAk1wa63arSWEHGLVmWS7JUvCM7 tSVQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1717430206; x=1718035006; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=0HOFtv9+hTvv/BrBRPyVlEYG3mY3IG/M5dOr58sRYAc=; b=gRL85u6veLo65fi++dbAFUTq7PIFmBEavDbF6j99aGIdhVtJcAcq8psiajy6GY2WZR EkvgT+U0G4t+1jhba3ZQ/gzNzM3W8axieL/S5AythsjmrsPFxaq8n/lGhLfQQlqG7tKp HIhtJZVKQy7tv2xO0OqKzLlUNH3CJCQu6zKW8bgGfRhHYRdW99kv37It+Kz2zgmfAbPM mLxaIHtdNp73fbHMvEwSAgvTGCtLg+PJgjwZN6DFFhbLoS0zxoXBIauwecYtuJoGPWIJ 1+UzEWT6BAVICh+Zxutz74Dbi+QAOiAGz3FeOmi47/cMO5FjOL4uLASrXH4OlT2urNlE arPA== X-Gm-Message-State: AOJu0YzJDbWZpd2l7YxO53Cb3xI+/aMeECYvDVGOAvmlgGBgaeAe8FDE sRxrH5QndSBHPHaIXY+99ZzRtECA+Trato/ZAp4Usc3AkPt5drvnPh1HWd3TgTX7yxOzGWQUOKP 7xswpf4Ti4jGN2tbP3ij48p3P96A= X-Google-Smtp-Source: AGHT+IEYsO1FL2E1CTfGcYg5XYybSlWkMgqQft+DyAnPt1CAB5d+HXzlX2MoMJIRreB5xOs3EDrBRU6i5TVNfzjr4H0= X-Received: by 2002:a05:6102:aca:b0:48b:ae5b:b356 with SMTP id ada2fe7eead31-48bc21536femr9128343137.15.1717430205901; Mon, 03 Jun 2024 08:56:45 -0700 (PDT) In-Reply-To: <86bk4lq1lq.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:286456 Archived-At: --00000000000059749c0619fe615d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable > Please investigate what happens with our SIGWINCH handler (in > dispnew.c) in these cases. In the case mentioned above, in which: after killing a frame and resizing another one, new sections appear black. I reported it as bug #71343, since it's not related to GC like this bug. On Fri, 31 May 2024 at 18:27, Eli Zaretskii wrote: > > From: Daniel Clemente > > Date: Fri, 31 May 2024 17:09:29 +0000 > > Cc: Eli Zaretskii > > > > 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=E2=86=9271=E2=86=9261= =E2=86=9251=E2=86=9241=E2=86=9231=E2=86=9221=E2=86=9211=E2=86=921 > > 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=E2=86=9221=E2=86=9211=E2=86=921) > > > > - 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. > --00000000000059749c0619fe615d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
> Please investigate what happens with= our SIGWINCH handler (in
> dispnew.c) in these cases.

In the= case mentioned above, in which: after killing a frame and resizing another= one, new sections appear black.
I reported it as bug #71343, si= nce it's not related to GC like this bug.

On Fri, 31 May 2024 at 18:27, Eli Zaretskii <eliz@gnu.org> wrote:
> 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 sty= le
> 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 t= hem
> 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<= br> > is garbled
> - if I decrease the terminal size fast, e.g. 81=E2=86=9271=E2=86=9261= =E2=86=9251=E2=86=9241=E2=86=9231=E2=86=9221=E2=86=9211=E2=86=921
> lines, often Emacs doesn't notice all changes, and it may still re= port
> that FrameRows(tty) is e.g. 31 when it went further down to 1
> (31=E2=86=9221=E2=86=9211=E2=86=921)
>
> - in addition there's a more complex refresh bug (not about resizi= ng 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= 9;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 t= oo
> 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 i= ssue
> as this bug):

Please investigate what happens with our SIGWINCH handler (in
dispnew.c) in these cases.
--00000000000059749c0619fe615d--