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=dP oyJ2Cz4YzJi5OfsKWIf0sIPL9zZhwtXCX967Rta/WlhHo7uotQGbcxEdumpMPGF9 cklvtG8RIDA6yXVNFrR0brezIfgnm7XHDc0fsMokzsMF1UBgaPKwHYK1baWEKBYZ NQwJWscdwApIgSVy9zcxgsIGVreFkdqAA7Lq1MdW0= 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=zGkMT7S7 R5a6NgJOysiLsVsSJ40=; b=fWVP3opmKqLx8b5ZhvlqD0ZuynkurwUWX22nffx2 HoeoAv71nbRZiNd65CtWZoWo5oheJXng7dnh+UBQg/F330/rVjKhHJfNkU45wpmS CGCMucr7f/+axPwitkIdyz+njQnzl+DkncDzxCgkyV2ZxS6b/NcAivMDNpgEiDjB tMQ= 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=0.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-oa0-f43.google.com MIME-Version: 1.0 X-Received: by 10.182.144.136 with SMTP id sm8mr7040899obb.63.1386880961962; Thu, 12 Dec 2013 12:42:41 -0800 (PST) In-Reply-To: References:

<52A9DE77 DOT 3080507 AT cornell DOT edu> <877gba9g3d DOT fsf AT Rainer DOT invalid> <52A9EEBE DOT 3050100 AT cornell DOT edu> <20131212182522 DOT GA2863 AT ednor DOT casa DOT cgf DOT cx> <52AA1257 DOT 60806 AT cornell DOT edu> <20131212195418 DOT GA1722 AT ednor DOT casa DOT cgf DOT cx> Date: Thu, 12 Dec 2013 15:42:41 -0500 Message-ID: Subject: Fwd: 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 2:54 PM, Christopher Faylor wrote: > On Thu, Dec 12, 2013 at 02:45:27PM -0500, Ken Brown wrote: >>On 12/12/2013 1:25 PM, Christopher Faylor wrote: >>> On Thu, Dec 12, 2013 at 12:13:34PM -0500, Ken Brown wrote: >>>> On 12/12/2013 11:41 AM, Achim Gratz wrote: >>>>> Ken Brown writes: >>>>>>> ***MEMORY-ERROR***: emacs[2924]: GSlice: failed to allocate 2040 bytes >>>>>>> (alignment: 2048): Cannot allocate memory >>>>> >>>>> I'm seeing the same thing on Win7/64 Pro, both for 64bit and 32bit >>>>> Cygwin. Since I don't normally use the X11 Emacs, unfortunately I don't >>>>> know which update was introducing this, it used to worked OK a few weeks >>>>> ago. >>>> >>>> And do you also use Windows Defender? >>>> >>>> If this isn't BLODA, I'm completely stumped. >>> >>> Would running under strace help? >> >>It might. Achim or Mike (or anyone who can reproduce this problem), >>could you run "strace -o strace.out emacs-X11 -Q" and post strace.out >>somewhere? > > Btw, posting it somewhere is a good suggestion since strace output seems > to be giving spamassassin some problems lately, making it hard to send > here. Okay, here it is: https://drive.google.com/file/d/0B5QasYpFDUHeWGdsQ0RlWkk5Wm8/edit?usp=sharing I was watching this in Task Manager; the emacs-X11 process got up to around 400+ MB before dying with a segfault. BTW, I am beginning to think that the link with Windows Update is a red herring; I uninstalled all the updates from this morning, one by one, and emacs-X11 still failed. I then rolled back to a restore point from a couple of days ago, again to no effect. I don't know what changed, though; everything was working fine until this morning. -- 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