From: Nix <nix@esperi.org.uk>
To: Dmitry Antipov <dmantipov@yandex.ru>
Cc: 16093@debbugs.gnu.org
Subject: bug#16093: 24.3.50; Crash of emacs --daemon on killing X server
Date: Tue, 10 Dec 2013 23:39:33 +0000 [thread overview]
Message-ID: <8738m0s2bu.fsf@spindle.srvr.nix> (raw)
In-Reply-To: <52A604A7.6010104@yandex.ru> (Dmitry Antipov's message of "Mon, 09 Dec 2013 21:57:59 +0400")
On 9 Dec 2013, Dmitry Antipov stated:
> On 12/09/2013 07:58 PM, Nix wrote:
>> It is fairly clear that we should not be calling xftfont_close() if the
>> X server is not there! Why has this started happening?
>
> Hm... IIUC there is no convenient way to check whether X display connection
> is alive. But we can do some tricks, for example, try to select() or poll()
> ConnectionNumber() - if there is no EBADF, X server is hopefully present...
Well, it's never happened before. Something has clearly changed... maybe
we're just cleaning up fonts much more lazily than before? (An ugly hack
to "fix" it in that case might just be to trigger a garbage-collect when
the last frame on a given terminal goes away.)
The Xlib error handler should really be being called, which suggests
this is a bug in Xft as well: I'll chase that up. (But that can't be the
cause of this: I last updated my Xft a year and a half ago.)
--
NULL && (void)
next prev parent reply other threads:[~2013-12-10 23:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-09 15:58 bug#16093: 24.3.50; Crash of emacs --daemon on killing X server Nix
2013-12-09 17:57 ` Dmitry Antipov
2013-12-10 19:43 ` Jan Djärv
2013-12-10 23:39 ` Nix [this message]
2013-12-11 0:20 ` Glenn Morris
2013-12-11 4:28 ` Dmitry Antipov
2013-12-13 22:35 ` Nix
2013-12-14 2:08 ` Dmitry Antipov
2013-12-16 7:52 ` Dmitry Antipov
2014-01-06 13:32 ` Nix
2013-12-11 6:01 ` Jan Djärv
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=8738m0s2bu.fsf@spindle.srvr.nix \
--to=nix@esperi.org.uk \
--cc=16093@debbugs.gnu.org \
--cc=dmantipov@yandex.ru \
/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).