public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
* emacs-X11 memory leak?
@ 2019-03-07 14:53 Rockefeller, Harry
  2019-03-07 15:09 ` Ken Brown
  0 siblings, 1 reply; 7+ messages in thread
From: Rockefeller, Harry @ 2019-03-07 14:53 UTC (permalink / raw)
  To: cygwin

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.


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: emacs-X11 memory leak?
  2019-03-07 14:53 emacs-X11 memory leak? Rockefeller, Harry
@ 2019-03-07 15:09 ` Ken Brown
  2019-03-07 15:38   ` Rockefeller, Harry
  2019-03-07 20:00   ` Rockefeller, Harry
  0 siblings, 2 replies; 7+ messages in thread
From: Ken Brown @ 2019-03-07 15:09 UTC (permalink / raw)
  To: cygwin

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1240 bytes --]

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
\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РÐ

^ permalink raw reply	[flat|nested] 7+ messages in thread

* RE: emacs-X11 memory leak?
  2019-03-07 15:09 ` Ken Brown
@ 2019-03-07 15:38   ` Rockefeller, Harry
  2019-03-07 20:00   ` Rockefeller, Harry
  1 sibling, 0 replies; 7+ messages in thread
From: Rockefeller, Harry @ 2019-03-07 15:38 UTC (permalink / raw)
  To: cygwin

[-- 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РÐ

^ permalink raw reply	[flat|nested] 7+ messages in thread

* RE: emacs-X11 memory leak?
  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
  1 sibling, 1 reply; 7+ messages in thread
From: Rockefeller, Harry @ 2019-03-07 20:00 UTC (permalink / raw)
  To: cygwin

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1094 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.

\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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: emacs-X11 memory leak?
  2019-03-07 20:00   ` Rockefeller, Harry
@ 2019-03-07 20:22     ` Ken Brown
  2019-03-07 21:40       ` Rockefeller, Harry
  0 siblings, 1 reply; 7+ messages in thread
From: Ken Brown @ 2019-03-07 20:22 UTC (permalink / raw)
  To: cygwin

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1417 bytes --]

On 3/7/2019 3:00 PM, Rockefeller, Harry wrote:
> 
>>> -----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
\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РÐ

^ permalink raw reply	[flat|nested] 7+ messages in thread

* RE: emacs-X11 memory leak?
  2019-03-07 20:22     ` Ken Brown
@ 2019-03-07 21:40       ` Rockefeller, Harry
  2019-03-08 12:06         ` Corinna Vinschen
  0 siblings, 1 reply; 7+ messages in thread
From: Rockefeller, Harry @ 2019-03-07 21:40 UTC (permalink / raw)
  To: cygwin

[-- 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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: emacs-X11 memory leak?
  2019-03-07 21:40       ` Rockefeller, Harry
@ 2019-03-08 12:06         ` Corinna Vinschen
  0 siblings, 0 replies; 7+ messages in thread
From: Corinna Vinschen @ 2019-03-08 12:06 UTC (permalink / raw)
  To: Rockefeller, Harry; +Cc: cygwin

[-- 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 --]

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2019-03-08 12:06 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-03-07 14:53 emacs-X11 memory leak? 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 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).