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=S7Y/Xbix58HubVGpHvA2MlPpciyUsQPrEEpNE5ptFSO g6MDNSMYa6oZoraVW2XAb5M1FJO36pjliiZkiomJ7cY+1L+XZaafvm7elrI179LV ypN74kyRqceMYmuLj+FFyuAoQsVWZ3ghS5htPpii1878vS2E3KucnqOJV5H9onSM = 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=ikBFTApl0LmQfqJAVB3MGSVK2B0=; b=EVILfxlCO6EFmgWHQ jYfthaoI3u+KWKOxwducz4LOftJQByPPK7m3Cnpp10848vhK/G7bxQcHhthLrHIH IpZ+ZrKaIl3is++Bwcn2Ij5FxUxpobcUA5wmv3qZHZlPU+v2hyqiZ/IcL+6UMy1e 4gvSxIYF01HoK1tfKbxS8J10Nc= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , 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: limerock02.mail.cornell.edu X-CornellRouted: This message has been Routed already. Message-ID: <52A9DE77.3080507@cornell.edu> Date: Thu, 12 Dec 2013 11:04:07 -0500 From: Ken Brown 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: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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) > > There was a previous report of this problem from last October (see > http://cygwin.com/ml/cygwin/2013-10/msg00149.html), but there was no > resolution in that thread. > > emacs-w32 runs without problems, and that's an acceptable workaround > for me at the moment, so this isn't an urgent issue for me currently. > I'll be appreciative of any insights, however. Does the problem occur with "emacs -Q"? Have you checked http://cygwin.com/faq/faq.html#faq.using.bloda ? 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