[debbugs-tracker] bug#14766: closed (24.3.50; sometimes "Memory exhausted" on Cygwin)

[GNU bug Tracking System]

Your message dated Wed, 17 Jul 2013 15:36:01 +0900
with message-id <address@hidden>
and subject line Re: bug#14766: 24.3.50; sometimes "Memory exhausted" on Cygwin
has caused the debbugs.gnu.org bug report #14766,
regarding 24.3.50; sometimes "Memory exhausted" on Cygwin
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
14766: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=14766
GNU Bug Tracking System
Contact address@hidden with problems
> --- Begin Message ---
>
>
>
> 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.
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#14766: 24.3.50; sometimes "Memory exhausted" on Cygwin
>
>
>
>
> Date: 
>
> Wed, 17 Jul 2013 15:36:01 +0900
>
>
>
>
> User-agent: 
>
> Gnus/5.130008 (真 Gnus v0.8) Emacs/24.3.50 (i686-pc-cygwin)
>
>
>
>
> 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
>
>
> --- End Message ---