From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 35961@debbugs.gnu.org
Subject: bug#35961: 27.0.50; Sometimes frame freezes and stops updating (almost entirely)
Date: Mon, 10 Jun 2019 02:40:03 +0300 [thread overview]
Message-ID: <e51bbb61-0aaf-1e12-86aa-7fa64607381f@yandex.ru> (raw)
In-Reply-To: <83lfymwsql.fsf@gnu.org>
On 31.05.2019 18:25, Eli Zaretskii wrote:
> Yes, but if you are thinking about some thread in that
> toolkit/windowing library getting stuck while others continue working,
> you can try starting Emacs in X synchronous mode (etc/DEBUG has the
> details), then Emacs will wait for each X call to return, and X will
> not return until the request completes. If you see the same problem
> in that case, i.e. some frame(s) become not responsive while others
> don't, it is almost certainly not an Emacs problem.
Thanks, I'll look into that if the problem persists (and if I can find a
repro).
The last time it happened, though, I observed the same effect in another
program, so this is probably not Emacs's fault. And I haven't seen the
problem since the day this bug was filed.
next prev parent reply other threads:[~2019-06-09 23:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 15:06 bug#35961: 27.0.50; Sometimes frame freezes and stops updating (almost entirely) Dmitry Gutov
[not found] ` <handler.35961.B.155905621510564.ack@debbugs.gnu.org>
2019-05-28 15:15 ` bug#35961: Acknowledgement (27.0.50; Sometimes frame freezes and stops updating (almost entirely)) Dmitry Gutov
2019-05-28 16:04 ` bug#35961: 27.0.50; Sometimes frame freezes and stops updating (almost entirely) Basil L. Contovounesios
2019-05-30 16:30 ` Dmitry Gutov
2019-05-30 17:05 ` Basil L. Contovounesios
2019-05-30 17:37 ` Dmitry Gutov
2019-05-30 20:25 ` Basil L. Contovounesios
2019-05-28 18:41 ` Eli Zaretskii
2019-05-30 16:37 ` Dmitry Gutov
2019-05-31 15:25 ` Eli Zaretskii
2019-06-09 23:40 ` Dmitry Gutov [this message]
2019-09-25 14:42 ` Lars Ingebrigtsen
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=e51bbb61-0aaf-1e12-86aa-7fa64607381f@yandex.ru \
--to=dgutov@yandex.ru \
--cc=35961@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 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).