[I sent this message a few weeks ago but did not get a response.
I hope we have someone who can help.]
Is there someone who knows how to trace X commands
to see what Emacs is sending that causes this memory leak?
Please send me mail if you can do it.

I can take a look. xmon can be used to trace X traffic. It is possible
that some X window is not deleted when updating the menus. But I'll see
if I can find anything.

It turns out that no xmon was needed. It is a general memory leak that is
present on all systems. It is both a leak in Emacs and a leak in the X server,
since X windows aren't being deallocated. I think this should go into RC. Is
it OK to put it in there (see attachement)? I've tested it under XFree86,
GNU/Linux and Solaris ix86.

Jan D.

Date: Thu, 9 Jan 2003 15:02:47 +0000
From: Alan Morgan <address@hidden>
To: address@hidden
Subject: Sun X server memory leak when running emacs 21.2
Sender: address@hidden
This bug report will be sent to the Free Software Foundation,
not to your local site managers!
Please write in English, because the Emacs maintainers do not have
translators to read other languages for them.
Your bug report will be posted to the address@hidden mailing list,
and to the gnu.emacs.bug news group.
In GNU Emacs 21.2.2 (sparc-sun-solaris2.6, OSF/Motif Version 1.2.6)
of 2002-08-08 on athene

On Sun Solaris 2.6, when running emacs 21.2 with the menu bar enabled,
the Sun
X server's memory usage increases with time, eventually making the
machine
unreasonably slow. This does not occur in emacs 20, nor in 21.2 if
the menu

bar is disabled.

To see the behaviour, start an X login session, monitor the virtual
memory
size of the Xsun process, and start a vanilla emacs with emacs -q.
When emacs
processes commands, the Xsun memory usage is seen to rise, usually in
chunks
of around 4-32k at a time. Opening files (with C-x C-f) and killing
buffers
(C-x C-k), with no other activity, seems to show the behaviour. If
emacs is

left undisturbed (no input) then the memory usage does not rise but stays

I am aware that this could be a bug in Xsun, not in emacs, but I'm
sorry I
don't know enough about the internals of X to know whether it is
possible for
an application to legitimately cause the Xsun process to expand, or if
this
has to imply a bug in the X implementation. I'd be interested to know
which is