all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Phil Sainty <psainty@orcon.net.nz>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 75461@debbugs.gnu.org
Subject: bug#75461: 30.0.93; Frequent (but inconsistent) hangs when creating frames
Date: Fri, 10 Jan 2025 02:25:51 +1300	[thread overview]
Message-ID: <5e6dd63525ab2e8a0282ff3bc71d8499@webmail.orcon.net.nz> (raw)
In-Reply-To: <86zfk0167o.fsf@gnu.org>

Well I don't know what the connection is, but I've now realised that
this seems to happen only when my *mu4e-headers* buffer (for the mu4e
email client) is visible.  As soon as I opened that I could reproduce
the problem again, and it seems to be a consistent trigger.

I'm using the version of mu4e which is packaged for Ubuntu 22.04:

Package: mu4e
Source: maildir-utils
Version: 1.4.15-1

That version is a few years old -- https://www.djcbsoftware.nl/code/mu/
says mu/mu4e 1.4 was released on 2020-04-18 -- but I'm using that
version to align with the packaged version of mu itself (the Ubuntu
package name for that one is "maildir-utils"), so I can't trivially
switch to a newer release.

On 2025-01-10 02:12, Eli Zaretskii wrote:
> Btw, by "hangs" you mean it is stuck doing nothing, right?  It
> doesn't use 100% of some CPU execution unit (that would be
> "infloops", not "hangs"), right?

No, I did mean an infinite loop (the "hang" was that this causes
the user interface to freeze up unless I signal the process).


> Run Emacs normally, not from GD, and when it hangs attach GDB to it
> and say
> 
>   (gdb) thread apply all bt
> 
> Then post here everything GDB produces.

Ok.  It's too late to continue with this right now, so I'll follow
this up later...


-Phil






  reply	other threads:[~2025-01-09 13:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-09 12:09 bug#75461: 30.0.93; Frequent (but inconsistent) hangs when creating frames Phil Sainty
2025-01-09 13:12 ` Eli Zaretskii
2025-01-09 13:25   ` Phil Sainty [this message]
2025-01-09 14:18     ` 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

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

  git send-email \
    --in-reply-to=5e6dd63525ab2e8a0282ff3bc71d8499@webmail.orcon.net.nz \
    --to=psainty@orcon.net.nz \
    --cc=75461@debbugs.gnu.org \
    --cc=eliz@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 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.