From: Unknown <ax487@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 37895@debbugs.gnu.org
Subject: bug#37895: 26.3; X protocol error: BadLength (poly request too large or internal Xlib length error) on protocol request 139
Date: Thu, 24 Oct 2019 17:34:00 +0200 [thread overview]
Message-ID: <2bc605b7f4bce3cdf8a705b31ba8b1667cfe461b.camel@gmx.de> (raw)
In-Reply-To: <83k18uxn29.fsf@gnu.org>
On Thu, 2019-10-24 at 16:58 +0300, Eli Zaretskii wrote:
> > From: Unknown <ax487@gmx.de>
> > Date: Thu, 24 Oct 2019 00:14:13 +0200
> >
> > Emacs crashes after triggering an X error message.
> >
> > To reproduce the error, I have to start emacs as a daemon via
> >
> > > emacs --fg-daemon
> >
> > and a client via
> >
> > > emacsclient -create-frame --alternate-editor=""
> >
> > As soon as I open a source file (C++ in my case), emacs crashes
> > immediately based on the following X error:
>
> Does this happen with _any_ file or just some? If the latter, can
> you
> try to figure out what is special about those files?
>
> If this happens with any file, does it also happen with pure ASCII
> files, like the README files in the Emacs distribution?
No, if I open the README, then everything works normally.
>
> > Note: the bug seems to be very similar to the
> > one reported here:
> >
> > https://debbugs.gnu.org/cgi/bugreport.cgi?bug=30874#33
> >
> > My emacs is (naturally) heavily modded, and I was not able to
> > pinpoint
> > the problem to one concrete package. Noticably, I *can* enter the
> > unicode symbol 274c.
>
> The backtrace seems to indicate that Emacs crashed trying to open
> some
> font, so tracing the fonts Emacs loads might give a hint wrt what
> goes
> wrong.
I have not included any additional fonts myself, but I guess the theme
does.
Regarding the tracing: As far as I can see the bottommost emacs code
being called is
static Lisp_Object
xftfont_open (struct frame *f, Lisp_Object entity, int pixel_size)
I also got
(gdb) call debug_print(entity)
#<font-entity xft GOOG JoyPixels nil iso10646-1 normal normal normal 0
nil nil 0 ((:font-entity "/usr/share/fonts/TTF/JoyPixels.ttf" . 0))>
Does that help?
>
> Thanks.
next prev parent reply other threads:[~2019-10-24 15:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 22:14 bug#37895: 26.3; X protocol error: BadLength (poly request too large or internal Xlib length error) on protocol request 139 Unknown
2019-10-24 13:58 ` Eli Zaretskii
2019-10-24 15:34 ` Unknown [this message]
2019-10-24 16:22 ` Eli Zaretskii
2019-10-24 18:06 ` Unknown
2019-10-25 16:37 ` Robert Pluim
[not found] ` <e0f168af7a18e4cbeadacfe2fad997d2b72a6909.camel@gmx.de>
2019-10-27 8:09 ` Robert Pluim
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=2bc605b7f4bce3cdf8a705b31ba8b1667cfe461b.camel@gmx.de \
--to=ax487@gmx.de \
--cc=37895@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.