X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	q=dns; s=default; b=kEtXWTGjpWwGg+zOBoGGImdlOnxJfrlis16xn9OpUDv
	ZsEfaye/CSnIujWZPqojYxNIc5VkQIY7bR5n4L0vb4FjvDIeBB+mLGzo+0nufz1W
	wWPcn0NSlayrzlqskcRliMavvGt0vP0j4miyfKbIsSHQbnsZWdIwOtAhv52286UI
	=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	s=default; bh=cmYylKSpiDw71GjisSlK8lf/spY=; b=bGYZeDQttWshFdIAF
	9I5YjX7SxcV8M3fRr5WoC5kVVoRQZ8Omq5IoAZF2pnoRiwHZiGevgsv3nBU43Edc
	drlJ+1itFsgYZpG7zmHs/EiKO7muEO9PeUpyQXzCYi9LlMtFV8+SpPA64DSo7ifP
	6bL3Ek51nodCH5nAL0dVKFcMJE=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-1.7 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2
X-HELO:	limerock04.mail.cornell.edu
X-CornellRouted:	This message has been Routed already.
Message-ID:	<52A9E472.7050206@cornell.edu>
Date:	Thu, 12 Dec 2013 11:29:38 -0500
From:	Ken Brown <kbrown AT cornell DOT edu>
User-Agent:	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version:	1.0
To:	cygwin AT cygwin DOT com
Subject:	Re: Fwd: emacs-X11 memory problem after Windows update
References:	<CAH5rLZWNvJLogZt=N16ri4=A9TE2_iwN2uW3WdZEWY8T5Xknfg AT mail DOT gmail DOT com> <CAH5rLZUCwde-PcCOdNVZaV-itW33XdA=NOSWbtC-A-wTh1uSdw AT mail DOT gmail DOT com> <52A9DE77 DOT 3080507 AT cornell DOT edu> <CAH5rLZUqWqb=MvycqB_QiZv5icUh2_51Ue0rYCY6gGDvvbP4uw AT mail DOT gmail DOT com>
In-Reply-To:	<CAH5rLZUqWqb=MvycqB_QiZv5icUh2_51Ue0rYCY6gGDvvbP4uw@mail.gmail.com>
X-IsSubscribed:	yes

On 12/12/2013 11:17 AM, William M. (Mike) Miller wrote:
> On Thu, Dec 12, 2013 at 11:04 AM, Ken Brown <kbrown AT cornell DOT edu> wrote:
>> On 12/12/2013 10:13 AM, William M. (Mike) Miller wrote:
>>>
>>> I'm running Windows 8.1 (cygcheck.out attached) and did a Windows
>>> update this morning.  Since then I cannot run emacs-X11.  Sometimes
>>> the message is:
>>>
>>> Memory exhausted--use M-x save-some-buffers then exit and restart Emacs
>>>
>>> Often there is no message.  Once I got:
>>>
>>> ***MEMORY-ERROR***: emacs[2924]: GSlice: failed to allocate 2040 bytes
>>> (alignment: 2048): Cannot allocate memory
>>>
>>> Fatal error 6: AbortedAbort (core dumped)
>> Does the problem occur with "emacs -Q"?
>
> Yes.
>
>> Have you checked http://cygwin.com/faq/faq.html#faq.using.bloda ?
>
> I hadn't previously.  The only thing on that list that I run, to the
> best of my knowledge, is Windows Defender.  I turned off real-time
> checking and tried emacs-X11 again, with the same result (a "Memory
> exhausted" error).

I'm not sure turning off real-time protection is enough.  Can you 
actually disable Windows Defender completely?

Ken

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

- Raw text -