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.m.mil...@gmail.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
