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:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; q=dns; s=default; b=cT c3XLlB19YJBwf4Bbi8mO5jX2gLs79CbY3KTuau7HkzjZa/tTH4pKYafAD5qP4IJx 75lYZbXGEemMh/Ft37McA0rJkAB0YIbD+uXW3TTuBfLMyhOP2K9ioD5jWCsEpbh/ TF+YanxW/fZm3GwuxrJiiA5QZ4x8dnma39+ebTSC0= 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:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; s=default; bh=nEyy8Z3l Zfw1kfDnp2gpgmQj1S4=; b=j+jLf3VAVGOAG50rK+La8/C/F6GWCYLLQKD+xFLw pTHtMi0fHGGBbKM7HZ4sE3aubJWK25CumyP9KH5uoLyxQdynKtbGLd5+yc4gvKOk MJJ7u26upLZk157yaq0seX/GPv6dQINSrm/gju01a2RODN3tJJyPwkCbrrps1Lhv 1WI= 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.6 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-ob0-f175.google.com MIME-Version: 1.0 X-Received: by 10.182.65.36 with SMTP id u4mr5957855obs.31.1386865052224; Thu, 12 Dec 2013 08:17:32 -0800 (PST) In-Reply-To: <52A9DE77.3080507@cornell.edu> References: <52A9DE77 DOT 3080507 AT cornell DOT edu> Date: Thu, 12 Dec 2013 11:17:32 -0500 Message-ID: Subject: Re: Fwd: emacs-X11 memory problem after Windows update From: "William M. (Mike) Miller" To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes On Thu, Dec 12, 2013 at 11:04 AM, Ken Brown 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). -- William M. (Mike) Miller | Edison Design Group william DOT m DOT miller AT gmail DOT com -- 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