From: John Shahid <jvshahid@gmail.com>
To: martin rudalics <rudalics@gmx.at>
Cc: 34260@debbugs.gnu.org
Subject: bug#34260: 27.0.50; Emacs randomly hangs during redisplay
Date: Thu, 31 Jan 2019 09:07:26 -0500 [thread overview]
Message-ID: <87imy4kjj5.fsf@gmail.com> (raw)
In-Reply-To: <5C52B28A.9080007@gmx.at>
martin rudalics <rudalics@gmx.at> writes:
>> Let me know how I can debug this issue further. Would the display
>> engine trace help in this case ? Emacs doesn't enter an infinite
>> recursion but from the CPU usage it is entering some sort of infinite
>> loop, but I can't figure out why.
>
> Please tell me if the following hold when the hang occurs:
>
> (1) You have at least two frames open.
Yes. EXWM creates a frame per monitor. I have two monitors which is
equivalent to two frames. I verified that by running `(frame-list)'
which gave me the following `(#<frame *Minibuf-1* 0x915df20> #<frame
*eshell* 0x1408c30>)'.
> (2) You run an externl process (likely shell) in a non-selected frame.
Very likely. I didn't what to look for when this happened, but I almost
always have an eshell/ansi-term window open.
> (3) The minibuffer window of the selected frame is or should be enlarged.
I am not sure. In the stacktraces I looked at there was always a call
to `message', but I'm not sure what are the args to it. Due to the
nature of my setup (i.e. using EXWM/Emacs as the window manager), when
this happen it is little hard to debug from inside Emacs and I have to
use gdb. I am not sure how to get the args from gdb.
JS
next prev parent reply other threads:[~2019-01-31 14:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 20:32 bug#34260: 27.0.50; Emacs randomly hangs during redisplay John Shahid
2019-01-30 21:46 ` Michael Heerdegen
2019-01-31 3:39 ` Eli Zaretskii
2019-01-31 8:32 ` martin rudalics
2019-01-31 14:07 ` John Shahid [this message]
2019-01-31 18:43 ` martin rudalics
2019-02-01 15:26 ` John Shahid
2019-02-02 9:29 ` martin rudalics
2019-02-02 17:09 ` John Shahid
2019-02-11 22:02 ` John Shahid
2019-02-19 8:36 ` martin rudalics
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=87imy4kjj5.fsf@gmail.com \
--to=jvshahid@gmail.com \
--cc=34260@debbugs.gnu.org \
--cc=rudalics@gmx.at \
/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).