From: "Stephen J. Turnbull" <stephen@xemacs.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: "Óscar Fuentes" <ofv@wanadoo.es>, emacs-devel@gnu.org
Subject: Re: X resource leak?
Date: Mon, 19 Jan 2009 15:33:11 +0900 [thread overview]
Message-ID: <87fxjfzty0.fsf@xemacs.org> (raw)
In-Reply-To: <87d4ek3s9j.fsf@cyd.mit.edu>
Chong Yidong writes:
> Óscar Fuentes <ofv@wanadoo.es> writes:
>
> > I place an emacs -Q session and a konsole with xrestop side to
> > side. Just opening a file, scrolling through, etc, makes the number of
> > pixmaps and misc objects to grow. Killing the buffer does not reduce the
> > number of X resources used by emacs. Something as simple as C-x C-f C-g
> > increases the number of pixmaps by 4 (2 for C-x C-f and two more when I
> > abort with C-g). Is as if the allocated X resources never were freed.
>
> I can not reproduce this. Could you provide a *precise* recipe?
This sounds like the X server may not have the X Render extension
enabled, so Xft is using pixmaps to simulate X Render. I have nothing
more to say about it, this is just hearsay from something I read
somewhere in passing (that for a couple of year Xft has had the
capability to use standard X calls to simulate X Render calls).
Anyway, it's easy to check for the X Render extension in the server
with xpdyinfo | grep -i render and in emacs with ldd | grep -i render.
If it's present as an extension in the server and linked in emacs,
probably that's not it.
next prev parent reply other threads:[~2009-01-19 6:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 2:59 X resource leak? Óscar Fuentes
2009-01-16 15:20 ` Chong Yidong
2009-01-18 16:01 ` Óscar Fuentes
2009-01-19 3:10 ` Chong Yidong
2009-01-19 6:33 ` Stephen J. Turnbull [this message]
2009-01-19 9:08 ` Óscar Fuentes
2009-01-19 9:18 ` Werner LEMBERG
2009-01-19 9:23 ` Óscar Fuentes
2009-01-19 12:03 ` Jan D.
2009-01-19 15:57 ` Óscar Fuentes
2009-01-20 5:51 ` Jan Djärv
2009-01-20 12:02 ` Óscar Fuentes
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=87fxjfzty0.fsf@xemacs.org \
--to=stephen@xemacs.org \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=ofv@wanadoo.es \
/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.