GNU bug report logs - #14766
24.3.50; sometimes "Memory exhausted" on Cygwin

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 14766 in the body.
You can then email your comments to 14766 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Katsumi Yamaoka <yamaoka <at> jpl.org>
To: bug-gnu-emacs <at> gnu.org
Subject: 24.3.50; sometimes "Memory exhausted" on Cygwin
Date: Tue, 02 Jul 2013 22:57:21 +0900

Hi,

This sometimes happens on Cygwin since the beginning of Jun
concurrently with Bug#14569 (bootstrap fails on Cygwin):

Memory exhausted--use C-x s then exit and restart Emacs
Error running timer `display-time-event-handler': (error "Memory exhausted--use C-x s then exit and restart Emacs")
Memory exhausted--use C-x s then exit and restart Emacs [3 times]

At that time I can do neither `C-x s' nor exit; what I can do
then is only to kill the Emacs process (so I transcribed the above
messages by hand).

Thanks.

Message #8 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Angelo Graziosi <angelo.graziosi <at> alice.it>
To: bug-emacs <bug-gnu-emacs <at> gnu.org>
Subject: Re: bug#14766: 24.3.50; sometimes "Memory exhausted" on Cygwin
Date: Tue, 02 Jul 2013 16:15:42 +0200

Katsumi Yamaoka wrote:
> This sometimes happens on Cygwin since the beginning of Jun
> concurrently with Bug#14569 (bootstrap fails on Cygwin):
>
> Memory exhausted--use C-x s then exit and restart Emacs
> Error running timer `display-time-event-handler': (error "Memory exhausted--use
> C-x s then exit and restart Emacs")
> Memory exhausted--use C-x s then exit and restart Emacs [3 times]
>
> At that time I can do neither `C-x s' nor exit; what I can do
> then is only to kill the Emacs process (so I transcribed the above
> messages by hand).

Hmm.. I never have seen that..

Where you see those messages? May you give a recipe to reproduce them?

Here Emacs trunk works... Usaually I start it with at least 11 buffers, 
a single frame and 3 windows.. it runs for hours with no problem.


Ciao,
Angelo.

Message #11 received at 14766 <at> debbugs.gnu.org (full text, mbox):

From: Ken Brown <kbrown <at> cornell.edu>
To: Katsumi Yamaoka <yamaoka <at> jpl.org>
Cc: 14766 <at> debbugs.gnu.org
Subject: Re: bug#14766: 24.3.50; sometimes "Memory exhausted" on Cygwin
Date: Tue, 02 Jul 2013 15:56:25 -0400

On 7/2/2013 9:57 AM, Katsumi Yamaoka wrote:
> Hi,
>
> This sometimes happens on Cygwin since the beginning of Jun
> concurrently with Bug#14569 (bootstrap fails on Cygwin):

We've since found the cause of that bug, and it affected only 
noninteractive uses of emacs.  So I don't think there's any connection 
between that bug and this one.

Angelo already asked for a recipe to reproduce the problem.  I realize 
that may be difficult if the problem is intermittent.  If you can't do 
that, then it would really help if you could pin down the exact bzr 
revision at which the problem first occurred.

Ken

Message #14 received at 14766 <at> debbugs.gnu.org (full text, mbox):

From: Katsumi Yamaoka <yamaoka <at> jpl.org>
To: Ken Brown <kbrown <at> cornell.edu>
Cc: 14766 <at> debbugs.gnu.org
Subject: Re: bug#14766: 24.3.50; sometimes "Memory exhausted" on Cygwin
Date: Wed, 03 Jul 2013 11:30:54 +0900

Ken Brown wrote:
> , then it would really help if you could pin down the exact bzr
> revision at which the problem first occurred.

It (bug#14569) started in the morning of 06 June, 2013 (in Japan).
I'm building bzr Emacs every morning of week days, so the suspected
revision will possibly be one of these:

revno: 112865
timestamp: Wed 2013-06-05 23:45:34 +0300 (Thu Jun  6 05:45:34 2013 +0900)
revno: 112859
timestamp: Wed 2013-06-05 10:04:13 -0700 (Thu Jun  6 02:04:13 2013 +0900)
revno: 112854
timestamp: Wed 2013-06-05 14:17:02 +0200 (Wed Jun  5 21:17:02 2013 +0900)
revno: 112851
timestamp: Tue 2013-06-04 21:58:43 -0400 (Wed Jun  5 10:58:43 2013 +0900)

Message #17 received at 14766 <at> debbugs.gnu.org (full text, mbox):

From: Katsumi Yamaoka <yamaoka <at> jpl.org>
To: Angelo Graziosi <angelo.graziosi <at> alice.it>, Ken Brown <kbrown <at> cornell.edu>
Cc: 14766 <at> debbugs.gnu.org
Subject: Re: bug#14766: 24.3.50; sometimes "Memory exhausted" on Cygwin
Date: Wed, 03 Jul 2013 11:31:01 +0900

Angelo Graziosi wrote:
> Katsumi Yamaoka wrote:
>> This sometimes happens on Cygwin since the beginning of Jun
>> concurrently with Bug#14569 (bootstrap fails on Cygwin):
>>
>> Memory exhausted--use C-x s then exit and restart Emacs
>> Error running timer `display-time-event-handler': (error "Memory
>> exhausted--use
>> C-x s then exit and restart Emacs")
>> Memory exhausted--use C-x s then exit and restart Emacs [3 times]
>>
>> At that time I can do neither `C-x s' nor exit; what I can do
>> then is only to kill the Emacs process (so I transcribed the above
>> messages by hand).

> Hmm.. I never have seen that..

I suspected it might be due to display-time-interval that was too
short (1), and turned back it to the default (60) about a month ago.
It didn't help after all, though.  Here is my Emacs clock setting:

(setq display-time-default-load-average nil
      display-time-24hr-format t)
;;(setq display-time-interval 1
;;      display-time-format "%H:%M:%S")
(display-time-mode 1)

> Where you see those messages? May you give a recipe to reproduce them?

It happens unexpectedly when I do something on Emacs, so I cannot
show a reproducible recipe.  But the frequency of this is much
less than the following:

Message-ID: <b4mfvvx66ut.fsf <at> jpl.org>
> Cygwin Emacs sometimes freezes for a couple of ten seconds
> unexpectedly.  It happens irregularly while I'm writing something.

Actually while I was writing this mail, "Memory exhausted" happened
only once, but the freezing happened for over ten times. :<

> Here Emacs trunk works... Usaually I start it with at least 11
> buffers, a single frame and 3 windows.. it runs for hours with no
> problem.

I'm encouraged with you and the active users anyway.  Thanks.

Message #20 received at 14766 <at> debbugs.gnu.org (full text, mbox):

From: Ken Brown <kbrown <at> cornell.edu>
To: Katsumi Yamaoka <yamaoka <at> jpl.org>
Cc: 14766 <at> debbugs.gnu.org, Paul Eggert <eggert <at> cs.ucla.edu>,
 Michael Albinus <michael.albinus <at> gmx.de>
Subject: Re: bug#14766: 24.3.50; sometimes "Memory exhausted" on Cygwin
Date: Tue, 02 Jul 2013 23:24:31 -0400

On 7/2/2013 10:30 PM, Katsumi Yamaoka wrote:
> Ken Brown wrote:
>> , then it would really help if you could pin down the exact bzr
>> revision at which the problem first occurred.
>
> It (bug#14569) started in the morning of 06 June, 2013 (in Japan).
> I'm building bzr Emacs every morning of week days, so the suspected
> revision will possibly be one of these:
>
> revno: 112865
> timestamp: Wed 2013-06-05 23:45:34 +0300 (Thu Jun  6 05:45:34 2013 +0900)
> revno: 112859
> timestamp: Wed 2013-06-05 10:04:13 -0700 (Thu Jun  6 02:04:13 2013 +0900)
> revno: 112854
> timestamp: Wed 2013-06-05 14:17:02 +0200 (Wed Jun  5 21:17:02 2013 +0900)
> revno: 112851
> timestamp: Tue 2013-06-04 21:58:43 -0400 (Wed Jun  5 10:58:43 2013 +0900)

In a different bug report you mentioned that you configure with the 
following options:

--with-x-toolkit=lucid --without-imagemagick --without-dbus 
--without-gconf --without-gsettings

Superficially it would seem that there's no reason for your build to 
link with glib.  But obviously it does link with glib, or else bug#14569 
wouldn't have affected you.  My guess is that revno 112830 on June 3, 
which introduced gfilenotify, is what caused your build to link with 
glib.  Is it possible that gfilenotify doesn't work well with the lucid 
toolkit?  Or perhaps the tickling of glib causes problems when the lucid 
toolkit is used?

Michael and Paul, do you have any ideas here?

Ken

Message #23 received at 14766 <at> debbugs.gnu.org (full text, mbox):

From: Paul Eggert <eggert <at> cs.ucla.edu>
To: Ken Brown <kbrown <at> cornell.edu>
Cc: 14766 <at> debbugs.gnu.org, Katsumi Yamaoka <yamaoka <at> jpl.org>,
 Michael Albinus <michael.albinus <at> gmx.de>
Subject: Re: bug#14766: 24.3.50; sometimes "Memory exhausted" on Cygwin
Date: Tue, 02 Jul 2013 21:54:55 -0700

On 07/02/2013 08:24 PM, Ken Brown wrote:
> Is it possible that gfilenotify doesn't work well with the lucid toolkit?
> Or perhaps the tickling of glib causes problems when the lucid toolkit is used?

It's possible, but lucid isn't multithreaded.

What happens if you append --without-file-notification
to the 'configure' options?  I expect that's what's
dragging in glib.

Message #26 received at 14766 <at> debbugs.gnu.org (full text, mbox):

From: Michael Albinus <michael.albinus <at> gmx.de>
To: Katsumi Yamaoka <yamaoka <at> jpl.org>
Cc: 14766 <at> debbugs.gnu.org, Paul Eggert <eggert <at> cs.ucla.edu>,
 Ken Brown <kbrown <at> cornell.edu>
Subject: Re: bug#14766: 24.3.50; sometimes "Memory exhausted" on Cygwin
Date: Wed, 03 Jul 2013 08:36:44 +0200

Katsumi Yamaoka <yamaoka <at> jpl.org> writes:

> It (bug#14569) started in the morning of 06 June, 2013 (in Japan).

Do you use autorevert? This would trigger gfilenotify, which has been
added June 3rd.

Best regards, Michael.

Message #29 received at 14766 <at> debbugs.gnu.org (full text, mbox):

From: Katsumi Yamaoka <yamaoka <at> jpl.org>
To: Paul Eggert <eggert <at> cs.ucla.edu>
Cc: 14766 <at> debbugs.gnu.org, Michael Albinus <michael.albinus <at> gmx.de>,
 Ken Brown <kbrown <at> cornell.edu>
Subject: Re: bug#14766: 24.3.50; sometimes "Memory exhausted" on Cygwin
Date: Wed, 03 Jul 2013 19:01:19 +0900

Paul Eggert wrote:
> On 07/02/2013 08:24 PM, Ken Brown wrote:
>> Is it possible that gfilenotify doesn't work well with the lucid toolkit?
>> Or perhaps the tickling of glib causes problems when the lucid
>> toolkit is used?

> It's possible, but lucid isn't multithreaded.

> What happens if you append --without-file-notification
> to the 'configure' options?  I expect that's what's
> dragging in glib.

I tried --without-file-notification.  AFAICT no difference presents,
if anything, I feel like the frequency of the freezing is increased.
Emacs links cygglib-2.0-0.dll .

Message #32 received at 14766 <at> debbugs.gnu.org (full text, mbox):

From: Katsumi Yamaoka <yamaoka <at> jpl.org>
To: Michael Albinus <michael.albinus <at> gmx.de>
Cc: 14766 <at> debbugs.gnu.org, Paul Eggert <eggert <at> cs.ucla.edu>
Subject: Re: bug#14766: 24.3.50; sometimes "Memory exhausted" on Cygwin
Date: Wed, 03 Jul 2013 19:01:27 +0900

Michael Albinus wrote:
> Katsumi Yamaoka <yamaoka <at> jpl.org> writes:
>> It (bug#14569) started in the morning of 06 June, 2013 (in Japan).

> Do you use autorevert? This would trigger gfilenotify, which has been
> added June 3rd.

I don't use auto-revert.

Message #35 received at 14766 <at> debbugs.gnu.org (full text, mbox):

From: Ken Brown <kbrown <at> cornell.edu>
To: Katsumi Yamaoka <yamaoka <at> jpl.org>
Cc: 14766 <at> debbugs.gnu.org, Paul Eggert <eggert <at> cs.ucla.edu>,
 Michael Albinus <michael.albinus <at> gmx.de>
Subject: Re: bug#14766: 24.3.50; sometimes "Memory exhausted" on Cygwin
Date: Wed, 03 Jul 2013 06:57:41 -0400

On 7/3/2013 6:01 AM, Katsumi Yamaoka wrote:
> Paul Eggert wrote:
>> On 07/02/2013 08:24 PM, Ken Brown wrote:
>>> Is it possible that gfilenotify doesn't work well with the lucid toolkit?
>>> Or perhaps the tickling of glib causes problems when the lucid
>>> toolkit is used?
>
>> It's possible, but lucid isn't multithreaded.
>
>> What happens if you append --without-file-notification
>> to the 'configure' options?  I expect that's what's
>> dragging in glib.
>
> I tried --without-file-notification.  AFAICT no difference presents,
> if anything, I feel like the frequency of the freezing is increased.
> Emacs links cygglib-2.0-0.dll .

What if you also add --without-rsvg?

Ken

Message #38 received at 14766 <at> debbugs.gnu.org (full text, mbox):

From: Katsumi Yamaoka <yamaoka <at> jpl.org>
To: Ken Brown <kbrown <at> cornell.edu>
Cc: 14766 <at> debbugs.gnu.org, Paul Eggert <eggert <at> cs.ucla.edu>,
 michael albinus <michael.albinus <at> gmx.de>
Subject: Re: bug#14766: 24.3.50; sometimes "Memory exhausted" on Cygwin
Date: Wed, 03 Jul 2013 20:48:53 +0900

Ken Brown wrote:
> On 7/3/2013 6:01 AM, Katsumi Yamaoka wrote:
>> Paul Eggert wrote:
>>> On 07/02/2013 08:24 PM, Ken Brown wrote:
>>>> Is it possible that gfilenotify doesn't work well with the lucid toolkit?
>>>> Or perhaps the tickling of glib causes problems when the lucid
>>>> toolkit is used?
>>
>>> It's possible, but lucid isn't multithreaded.
>>
>>> What happens if you append --without-file-notification
>>> to the 'configure' options?  I expect that's what's
>>> dragging in glib.
>>
>> I tried --without-file-notification.  AFAICT no difference presents,
>> if anything, I feel like the frequency of the freezing is increased.
>> Emacs links cygglib-2.0-0.dll .

> What if you also add --without-rsvg?

Oh, Emacs was built without glib.  It still sometimes freezes,
though I haven't seen "Memory exhausted" yet so far.  I'll keep
trying it.  Thanks.

Message #43 received at 14766-done <at> debbugs.gnu.org (full text, mbox):

From: Katsumi Yamaoka <yamaoka <at> jpl.org>
To: 14766-done <at> debbugs.gnu.org, 14569-done <at> debbugs.gnu.org
Cc: Paul Eggert <eggert <at> cs.ucla.edu>, michael albinus <michael.albinus <at> gmx.de>,
 Ken Brown <kbrown <at> cornell.edu>
Subject: Re: bug#14766: 24.3.50; sometimes "Memory exhausted" on Cygwin
Date: Wed, 17 Jul 2013 15:36:01 +0900

I'm closing these two bugs:

bug#14569: 24.3.50; bootstrap fails on Cygwin
bug#14766: 24.3.50; sometimes "Memory exhausted" on Cygwin

Katsumi Yamaoka wrote:
> Ken Brown wrote:
>> On 7/3/2013 6:01 AM, Katsumi Yamaoka wrote:
>>> Paul Eggert wrote:
>>>> On 07/02/2013 08:24 PM, Ken Brown wrote:
>>>>> Is it possible that gfilenotify doesn't work well with the lucid toolkit?
>>>>> Or perhaps the tickling of glib causes problems when the lucid
>>>>> toolkit is used?
>>>
>>>> It's possible, but lucid isn't multithreaded.
>>>
>>>> What happens if you append --without-file-notification
>>>> to the 'configure' options?  I expect that's what's
>>>> dragging in glib.
>>>
>>> I tried --without-file-notification.  AFAICT no difference presents,
>>> if anything, I feel like the frequency of the freezing is increased.
>>> Emacs links cygglib-2.0-0.dll .

>> What if you also add --without-rsvg?

> Oh, Emacs was built without glib.  It still sometimes freezes,
> though I haven't seen "Memory exhausted" yet so far.  I'll keep
> trying it.  Thanks.

I don't know why, sorry, but Emacs on Cygwin doesn't make the memory
exhausted, it doesn't freeze, and it bootstraps smoothly these days.
`system-configuration-options' I use now is:
	"--verbose --with-x-toolkit=lucid --without-imagemagick\
	--without-dbus --without-gconf --without-gsettings"
I.e., Emacs is built with glib.

Thanks.

As for the derived bug
"Emacs segfaulting on FreeBSD 9.1-RELEASE (amd64) during memory allocation."
that is labeled with bug#14569 (the same), I believe it's been solved:

http://thread.gmane.org/gmane.emacs.devel/161494/focus=75909

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.