From: Stefan Kangas <stefankangas@gmail.com>
To: Mike Kupfer <kupfer@rawbw.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 74535-done@debbugs.gnu.org
Subject: bug#74535: 30.0.92; partial hang, esp. keyboard events
Date: Wed, 1 Jan 2025 21:13:04 -0600 [thread overview]
Message-ID: <CADwFkmnFbS97GiMPVbsajFqcSTfCnqvUUBnAwoDU9VgkgudVUw@mail.gmail.com> (raw)
In-Reply-To: <46142.1735784926@alto.camomileplus.org>
Mike Kupfer <kupfer@rawbw.com> writes:
> Stefan Kangas wrote:
>
>> Eli Zaretskii <eliz@gnu.org> writes:
>
>> > So I guess we need to wait a few more weeks before we are sure.
>> >
>> > Thanks.
>>
>> That was over 3 weeks ago. Do we feel more confident now?
>
> I haven't seen the hang again. I went back to 30.0.92 on Dec 21, after
> hacking up a script that uses emacsclient to invoke view-lossage.
> (Rather than bisecting by changes to the code, at 4 weeks per iteration,
> I thought it might be more effective to try a bisection strategy based
> on the flow of data through Emacs. Depending on what view-lossage tells
> me--assuming I ever see the hang again--, I can add hacky logging code
> to my builds in whatever place seems appropriate. FWIW, prior to going
> back to 30.0.92, I diffed the changes from 30.0.91 to 30.0.92 and
> nothing seemed plausible as a possible cause.)
>
> At this point, I'm fine with calling the bug very rare and moving on.
> If it happens again, I'll see what information I can get and update the
> bug report.
Thanks for reporting back. I'm therefore closing this bug report.
Please report back if you see the hang again.
prev parent reply other threads:[~2025-01-02 3:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-25 19:13 bug#74535: 30.0.92; partial hang, esp. keyboard events Mike Kupfer
2024-11-25 19:27 ` Eli Zaretskii
2024-11-25 21:59 ` Mike Kupfer
2024-12-07 12:25 ` Eli Zaretskii
2024-12-08 2:23 ` Mike Kupfer
2024-12-08 6:11 ` Eli Zaretskii
2025-01-02 1:58 ` Stefan Kangas
2025-01-02 2:28 ` Mike Kupfer
2025-01-02 3:13 ` Stefan Kangas [this message]
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=CADwFkmnFbS97GiMPVbsajFqcSTfCnqvUUBnAwoDU9VgkgudVUw@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=74535-done@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=kupfer@rawbw.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.