This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: emacs-X11 memory leak?


>>> -----Original Message-----
>>> From: cygwin-owner@cygwin.com <cygwin-owner@cygwin.com> On Behalf Of
>>> Ken Brown
>>> Sent: Thursday, March 07, 2019 9:09 AM
>>>> To: cygwin@cygwin.com
>>>> Subject: Re: emacs-X11 memory leak?
>>
>>>> On 3/7/2019 9:53 AM, Rockefeller, Harry wrote:
>>>>> CYGWIN_NT-6.1 HARRYR-PC 3.0.1(0.338/5/3) 2019-02-20 10:19 x86_64
>>>>> Cygwin GNU Emacs 26.1 (build 1, x86_64-unknown-cygwin, GTK+ Version
>>>>> 3.22.28) of 2018-05-28
>>>>> This started happening about the time I upgraded to Cygwin 3.0.x.
>>>>
>>>> See http://www.cygwin.org/ml/cygwin/2019-03/msg00122.html, and try the latest cygwin snapshot.
>>
>>>> Ken
>
>>> Thank you.  I don't see the memory leak.
>> Running the latest snapshot of cygwin1.dll:
>> A few hours later now ...
>> Emacs crashed.  kill -9 PID did not remove it.
>> MS Task manager was used to kill it.
>> I don't see any obvious errors.

>I've been using a build of emacs-26.1.92 (a pretest for emacs-26.2) and haven't had any problems.  If you want to try it, you can install it >from my personal Cygwin repository:

>   http://sanibeltranquility.com/cygwin

>Ken

FWIW, after killing the locked up/frozen/hung emacs-X11.exe I restarted with emacs -Q& in an xterm and almost as
Soon as I used the mouse buttons in emacs it locked up again.
So, I'm trying the 2nd choice at your site, adding your repository to the default ones.
Running Cygwin1.dll, 6 march snapshot, and your latest test emacs. So far :-)

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]