This is the mail archive of the
cygwin-xfree@cygwin.com
mailing list for the Cygwin XFree86 project.
Re: GDI object leak with remote emacs
- From: Takuma Murakami <takuma at dgp dot ne dot jp>
- To: cygwin-xfree at cygwin dot com
- Date: Thu, 19 Feb 2004 21:41:49 +0900
- Subject: Re: GDI object leak with remote emacs
- References: <16426.44436.977811.58100@what.openface.ca>
- Reply-to: cygwin-xfree at cygwin dot com
Jeremy,
> I don't know if this is related to the problems that people are
> experiencing with local copies of emacs but I'm seeing a GDI object
> leak with remote invocations of emacs that are routed back to my X
> server.
>
> Basically, I run cygwin/XFree86 on my local workstation, and I start
> an emacs on a Unix server that is displayed on my X server here.
> When using emacs, everytime I open a file, I can see that the XWin.exe
> processes gains a few GDI objects, but killing that buffer in emacs
> doesn't free them. Exiting emacs doesn't free them either. Once the
> leak grows enough (around 1500 GDI objects in XWin.exe) I start
> getting repaint problems and I have to kill X and restart it.
I cannot reproduce this in the following environments.
- Cygwin DLL 1.5.5 and 1.5.7
- Cygwin/X release-44
- GNU Emacs 21.3 on FreeBSD 4.8 and 21.3 on MacOS X 10.3
- SFU not installed
- invoked by 'ssh -CXf <hostname> emacs'
In my task manager's process list XWin.exe allocates 2 GDI
objects for a frame and the number of open files does not
affect it. Closing a frame correctly reduces 2 GDI objects.
Takuma Murakami