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

Previous Next

Full log

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.

Previous Next

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