From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: "Rockefeller, Harry" <Harry.Rockefeller@flightsafety.com>
Cc: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: emacs-X11 memory leak?
Date: Fri, 08 Mar 2019 12:06:00 -0000 [thread overview]
Message-ID: <20190308120614.GH3785@calimero.vinschen.de> (raw)
In-Reply-To: <ea6941e4310e41c5812638ed689cc2b2@vsrv060ex03.ssd.fsi.com>
[-- Attachment #1: Type: text/plain, Size: 1056 bytes --]
On Mar 7 21:40, Rockefeller, Harry wrote:
> >>>> 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.
> [...]
> 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.
https://cygwin.com/ml/cygwin/2019-03/msg00160.html
Corinna
--
Corinna Vinschen
Cygwin Maintainer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-03-08 12:06 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
2019-03-08 12:06 ` Corinna Vinschen [this message]
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=20190308120614.GH3785@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=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).