public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
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 15:38:00 -0000	[thread overview]
Message-ID: <81001bf159cb4d60934d05c227e9a3cb@vsrv060ex03.ssd.fsi.com> (raw)
In-Reply-To: <0a4c268b-b2ab-31a7-e854-40acdf1a6e68@cornell.edu>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1750 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
>>
>> I got egg on my face with my last post to Cygwin.  So, no, I'm not
>> claiming there is a memory leak, but rather how to test what's going on.
>>
>> I don't know if this is relevant.  I got this error when I started emacs with -Q option:
>> ** (emacs:2017): WARNING **: Error retrieving accessibility bus
>> address: org.freedesktop.DBus.Error.Spawn.ChildExited: Process
>> org.a11y.Bus exited with status 1
>>
>> After opening one directory with C-x d the emacs-X11.exe memory (private working set) was 28,000K as reported by Windows Task Manager.
>> This continues to grow.  After 15 minutes it is now about 44,000K.
>>
>> 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
>Т  Х & & V  &W\x06 'G3 \x02\x02\x02\x02\x02\x02\x06 GG\x03   7 wv   6    & & V 2 F  Фd\x15\x13 \x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x06 GG\x03   7 wv   6   f\x17\x12 ФF 7V V F\x17F   \x02\x02\x02\x02\x02\x02\x02\x02\x06 GG\x03   7 >wv   6   F 72 F  ХV 7V'67& &R\x06  f \x02\x02\x02\x02\x02\x06 GG\x03   7 wv   6      7V 7V'67& &R 6  \x06 PР

Thank you.  I don't see the memory leak.
\0ТÒÐÐ¥\a&ö&ÆVÒ\a&W\x06÷'G3¢\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒ÷\a&ö&ÆV×2æ‡FÖÀФd\x15\x13¢\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöf\x17\x12ðФFö7VÖVçF\x17F–öã¢\x02\x02\x02\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöFö72æ‡FÖÀÐ¥Vç7V'67&–&R\x06–æfó¢\x02\x02\x02\x02\x02\x06‡GG\x03¢òö7–wv–âæ6öÒöÖÂò7Vç7V'67&–&R×6–×\x06ÆPРÐ

  reply	other threads:[~2019-03-07 15:38 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 [this message]
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

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=81001bf159cb4d60934d05c227e9a3cb@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).