From: "Rockefeller, Harry" <Harry.Rockefeller@flightsafety.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: emacs-X11 memory leak?
Date: Thu, 07 Mar 2019 21:40:00 -0000 [thread overview]
Message-ID: <ea6941e4310e41c5812638ed689cc2b2@vsrv060ex03.ssd.fsi.com> (raw)
In-Reply-To: <8e6f039f-098c-6563-2c90-bc5ece918bc1@cornell.edu>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1727 bytes --]
>>> -----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 :-)
\x03B‹KCB”\x1c›Ø›\x19[H\x1c™\^[Ü\x1cΈ\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÜ\x1c›Ø›\x19[\Ëš\x1d^[[\x03B‘TNˆ\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÙ˜\KÃB‘^[ØÝ[Y[\x18]\x1a[ÛŽˆ\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÙ^[ØÜËš\x1d^[[\x03B•[œÝXœØÜšX™H\x1a[™›Îˆ\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÛ[\vÈÝ[œÝXœØÜšX™K\Ú[\^[\x19CBƒB
next prev parent reply other threads:[~2019-03-07 21:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-07 14:53 Rockefeller, Harry
2019-03-07 15:09 ` Ken Brown
2019-03-07 15:38 ` Rockefeller, Harry
2019-03-07 20:00 ` Rockefeller, Harry
2019-03-07 20:22 ` Ken Brown
2019-03-07 21:40 ` Rockefeller, Harry [this message]
2019-03-08 12:06 ` Corinna Vinschen
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=ea6941e4310e41c5812638ed689cc2b2@vsrv060ex03.ssd.fsi.com \
--to=harry.rockefeller@flightsafety.com \
--cc=cygwin@cygwin.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.
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).