From: Mike Kupfer <m.kupfer@acm.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Need help debugging Emacs: emacsclient will not draw its contents sometimes
Date: Wed, 17 Feb 2016 21:01:15 -0800 [thread overview]
Message-ID: <1027.1455771675@allegro.localdomain> (raw)
In-Reply-To: Your message of "Wed, 17 Feb 2016 22:02:14 +0200." <83d1rvumux.fsf@gnu.org>
As suggested, I've opened a bug for this: #22728.
Eli Zaretskii wrote:
> > From: Mike Kupfer <m.kupfer@acm.org>
> > cc: emacs-devel@gnu.org
> > Date: Tue, 16 Feb 2016 18:05:52 -0800
> >
> > I ran "emacsclient -c" twice within a short period of time, and the
> > server log showed 2 frames being created. So *some* code in Emacs
> > thought the first frame was created, even though it didn't show up
> > in the output from (frame-list).
>
> This means Emacs started creating the frame, but didn't finish that
> process. A new frame is recorded in the frame list only when it is
> completely set up. The question is: what happens during that process
> which prevents it from completing?
>
> At this point, it looks like instrumenting x-create-frame to write
> traces to some file might tell what causes that function to stop doing
> its job half way through.
Okay. If someone provides a patch, I'd be happy to apply it on the
systems I run Emacs on. I can also look at instrumenting
x-create-frame myself. That will take longer to set up, but given how
long it is between occurrences of this problem, some initial delay
probably doesn't matter much.
I wonder if the problem is particular to a certain widget set. If
anyone has suggestions for instrumenting the Athena (2D) widget set, I'd
welcome them.
> > And I still think it's suspicious that the bad frame seems to match a
> > frame that was deleted earlier.
>
> Was the deleted frame deleted from the frame list?
I'm not sure I understand the question. The frame list that I looked at
on the 15th had these 3 frames:
(#<frame emacs@athyra 0x4eba368>
#<frame journal-2016.org 0x3073760>
#<frame *GNU Emacs* 0x1128268>)
(This was after the bad frame was created.)
The log showed the deletion of
#<frame Todo.krb5-issues 0x4343058>
on the 12th, and the creation of
#<frame emacs@athyra 0x4343058>
on the 15th. Let me know if that doesn't answer your question.
thanks and regards,
mike
next prev parent reply other threads:[~2016-02-18 5:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-08 13:00 Need help debugging Emacs: emacsclient will not draw its contents sometimes Jon Dufresne
2015-09-08 13:28 ` Tassilo Horn
2015-09-08 17:18 ` Eli Zaretskii
2015-09-08 18:58 ` Jon Dufresne
2015-09-08 19:16 ` Eli Zaretskii
2015-09-09 22:29 ` Jon Dufresne
2015-09-10 15:26 ` Eli Zaretskii
2015-09-10 18:20 ` Jon Dufresne
2015-09-10 18:46 ` Eli Zaretskii
2015-09-10 18:52 ` Jon Dufresne
2015-09-11 7:26 ` Eli Zaretskii
2015-09-11 16:47 ` Jon Dufresne
2015-09-14 10:09 ` Eli Zaretskii
2015-09-23 0:51 ` Jon Dufresne
2015-09-23 6:45 ` Eli Zaretskii
2015-09-27 22:21 ` Mike Kupfer
2015-09-28 6:39 ` Eli Zaretskii
2016-02-16 1:07 ` Mike Kupfer
2016-02-16 16:26 ` Eli Zaretskii
2016-02-16 16:38 ` Kaushal Modi
2016-02-16 16:44 ` Eli Zaretskii
2016-02-16 17:06 ` Kaushal Modi
2016-02-17 2:05 ` Mike Kupfer
2016-02-17 20:02 ` Eli Zaretskii
2016-02-18 5:01 ` Mike Kupfer [this message]
2016-02-20 11:24 ` 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
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=1027.1455771675@allegro.localdomain \
--to=m.kupfer@acm.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@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).