From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Jean Louis <bugs@gnu.support>
Cc: 58332@debbugs.gnu.org
Subject: bug#58332: 29.0.50; Crash on more fonts by family
Date: Fri, 07 Oct 2022 18:38:11 +0800 [thread overview]
Message-ID: <87v8ovq5po.fsf@yahoo.com> (raw)
In-Reply-To: <86leptqehp.fsf@protected.rcdrun.com> (Jean Louis's message of "Thu, 06 Oct 2022 16:16:18 +0300")
Jean Louis <bugs@gnu.support> writes:
> in Lucid toolkit, I choose Options, Set Default Font, More Fonts, By
> Family and Emacs crashes, I get this:
> $ gdb --args emacs -Q
> GNU gdb (GDB) 12.1
> Copyright (C) 2022 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.
> Type "show copying" and "show warranty" for details.
> This GDB was configured as "x86_64-pc-linux-gnu".
> Type "show configuration" for configuration details.
> For bug reporting instructions, please see:
> <https://www.gnu.org/software/gdb/bugs/>.
> Find the GDB manual and other documentation resources online at:
> <http://www.gnu.org/software/gdb/documentation/>.
>
> For help, type "help".
> Type "apropos word" to search for commands related to "word"...
> Reading symbols from emacs...
> (gdb) run
> Starting program: /home/data1/protected/bin/emacs -Q
> [Thread debugging using libthread_db enabled]
> Using host libthread_db library "/usr/lib/libthread_db.so.1".
> [New Thread 0x7ffff1be06c0 (LWP 4914)]
> [New Thread 0x7ffff13df6c0 (LWP 4915)]
> [Detaching after fork from child process 4916]
> [New Thread 0x7ffff0bde6c0 (LWP 4917)]
> X protocol error: BadAlloc (insufficient resources for operation) on protocol request 53
> Serial no: 11069
That is because you have too many fonts installed, and the X
server/library ran out of available memory/resource IDs trying to create
pixmanp to back all the panes and menus.
That is not a problem that can be easily fixed, at least without
developing some kind of lazy menu window creation mechanism.
It would be nice to not crash, though, instead just refusing to display
the window. I will look into that.
prev parent reply other threads:[~2022-10-07 10:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 13:16 bug#58332: 29.0.50; Crash on more fonts by family Jean Louis
2022-10-07 10:38 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
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=87v8ovq5po.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=58332@debbugs.gnu.org \
--cc=bugs@gnu.support \
--cc=luangruo@yahoo.com \
/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).