all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: 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: Wed, 05 Jun 2024 19:43:21 +0300	[thread overview]
Message-ID: <864ja7jq6u.fsf@gnu.org> (raw)
In-Reply-To: <867cf3junq.fsf@gnu.org> (message from Eli Zaretskii on Wed, 05 Jun 2024 18:06:49 +0300)

> Date: Wed, 05 Jun 2024 18:06:49 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 71289@debbugs.gnu.org
> 
> > From: Daniel Clemente <n142857@gmail.com>
> > Date: Wed, 5 Jun 2024 13:50:48 +0000
> > Cc: 71289@debbugs.gnu.org
> > 
> > With it (running on 799f78a92c6c31f4d181390523b83d036020ede1 with no
> > other changes), I still see the same types of crash that I already
> > reported: in tty_write_glyphs (see BT1 below) and in
> > build_frame_matrix_from_leaf_window (see BT2 below).
> > However they don't mention GC now.
> 
> So it is not exactly the same type of crash.
> 
> In what scenario does this happen now?  IOW, what did you do to
> trigger those crashes?
> 
> I'd like to ask you to run that scenario with a watchpoint on the
> variable delayed_size_change, and the following two watchpoint
> commands:
> 
>   bt 5
>   continue
> 
> I hope the backtraces produced by this will explain who resets the
> delayed_size_change flag, seemingly prematurely(?), and might suggest
> ideas for a solution.  (I have an idea already, but would like to see
> some data to make sure the idea is solid.)

I decided to go with my idea anyway, so please update from Git before
trying next, and if the problem is still there, try answering my
questions above.

Thanks.





  reply	other threads:[~2024-06-05 16:43 UTC|newest]

Thread overview: 37+ 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
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 [this message]
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-09-04  6:09                         ` Daniel Clemente
2024-09-04  6:21                           ` Daniel Clemente
2024-09-04 11:59                           ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=864ja7jq6u.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 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.