Re: Fwd: Fwd: emacs-X11 memory problem after Windows update

On Thu, Dec 12, 2013 at 5:20 PM, Ken Brown wrote: > On 12/12/2013 3:42 PM, William M. (Mike) Miller wrote: >> >> 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: >

Re: Fwd: Fwd: emacs-X11 memory problem after Windows update

On 12/12/2013 3:42 PM, William M. (Mike) Miller wrote: 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/201

Re: Fwd: emacs-X11 memory problem after Windows update

Ken Brown writes: > And do you also use Windows Defender? MSE (which I believe is just the "consumer" name for the same software). > If this isn't BLODA, I'm completely stumped. So far I've not had persistent problems with MSE (doesn't mean anything really… I know). Only when an application is

Fwd: Fwd: emacs-X11 memory problem after Windows update

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 w

Re: Fwd: emacs-X11 memory problem after Windows update

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

Re: Fwd: emacs-X11 memory problem after Windows update

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

Re: Fwd: emacs-X11 memory problem after Windows update

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

Re: Fwd: emacs-X11 memory problem after Windows update

On 12/12/2013 12:38 PM, William M. (Mike) Miller wrote: On Thu, Dec 12, 2013 at 11:29 AM, Ken Brown wrote: On 12/12/2013 11:17 AM, William M. (Mike) Miller wrote: 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 Windo

Re: Fwd: emacs-X11 memory problem after Windows update

On Thu, Dec 12, 2013 at 11:29 AM, Ken Brown wrote: > On 12/12/2013 11:17 AM, William M. (Mike) Miller wrote: >> >> 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

Re: Fwd: emacs-X11 memory problem after Windows update

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

Re: Fwd: emacs-X11 memory problem after Windows update

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

Re: Fwd: emacs-X11 memory problem after Windows update

On 12/12/2013 11:17 AM, William M. (Mike) Miller wrote: 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. Someti

Re: Fwd: emacs-X11 memory problem after Windows update

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

Re: Fwd: emacs-X11 memory problem after Windows update

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

Re: WG: Memory Problem with POSIX Thread under Windows XP

On Aug 22 09:03, Martin J?hren wrote: > Hello everyone, > > ich have a problem under Windows XP using CYGWIN 3.1.17(6)-release > (i686-pc-cygwin) with GCC 3.4.4 with the following code: > > > void *testThread(void *data) > { > double kk = 1.232231212; > printf("\r\n%f",kk); > //p

Re: WG: Memory Problem with POSIX Thread under Windows XP

On Tue, Aug 22, 2006 at 12:46:18PM +0100, Dave Korn wrote: >On 22 August 2006 11:09, Martin J?hren wrote: >>I tried following code with vs2005, and... there is no memory problem! >>So the bug must be located in CYGWIN or in GCC. Form now on it seems >>to me, that I really

RE: WG: Memory Problem with POSIX Thread under Windows XP

On 22 August 2006 11:09, Martin Jöhren wrote: > I tried following code with vs2005, and... there is no memory problem! So > the bug must be located in CYGWIN or in GCC. Form now on it seems to me, > that I really need help. Cause I'm not so familiar with deeper CYGWIN or GCC &

Re: WG: Memory Problem with POSIX Thread under Windows XP

I tried following code with vs2005, and... there is no memory problem! So the bug must be located in CYGWIN or in GCC. Form now on it seems to me, that I really need help. Cause I'm not so familiar with deeper CYGWIN or GCC problems. I'm looking foward for any ideas how to handle t

Re: WG: Memory Problem with POSIX Thread under Windows XP

Martin Jöhren, le Tue 22 Aug 2006 11:13:36 +0200, a écrit : > This indicates that the problem lies in the cygwin shell or in gcc or > it is a windows based problem, which could mean that windows is not > abled to free the threads as fast as the program creates new ones. Any > ideas? I doubt it may

Re: WG: Memory Problem with POSIX Thread under Windows XP

. There is also the same memory problem. This indicates that the problem lies in the cygwin shell or in gcc or it is a windows based problem, which could mean that windows is not abled to free the threads as fast as the program creates new ones. Any ideas? Martin Jöhren Hoppe Bordmesstechnik Tel:

Re: WG: Memory Problem with POSIX Thread under Windows XP

Hi, Martin Jöhren, le Tue 22 Aug 2006 09:03:03 +0200, a écrit : > printf("\r\n%f",kk); > If i compile and start the executing file I can see in the windows > taskmanager, that the memory used by the program increases continuesly every > second. If I change the code in the testThread function

WG: Memory Problem with POSIX Thread under Windows XP

Hello everyone, ich have a problem under Windows XP using CYGWIN 3.1.17(6)-release (i686-pc-cygwin) with GCC 3.4.4 with the following code: void *testThread(void *data) { double kk = 1.232231212; printf("\r\n%f",kk); //pthread_exit(NULL); return(NULL); } int main (int arg

RE: Shared memory problem

Original Message >From: CRAIG SORENSEN >Sent: 25 August 2005 15:56 > I have attached the cygcheck file and a short program that I have copied > from a tutorial online. I am compiling it as shown here: > > gcc shm_write.c -o shm_write > > There are no errors or warnings when I compile, bu

Re: Shared memory problem

Ugh, top-posting. Reformatted. On Thu, 25 Aug 2005, CRAIG SORENSEN wrote: > From: Igor Pechtchanski <[EMAIL PROTECTED]> > Reply-To: [EMAIL PROTECTED] > To: CRAIG SORENSEN <[EMAIL PROTECTED]> > CC: [EMAIL PROTECTED] . Thanks. > On Thu, 25 Aug 2005

Re: Shared memory problem

On Thu, 25 Aug 2005, CRAIG SORENSEN wrote: > I have followed the instructions in the README file and the messages > already sent about this subject. The cygserver is set up and running, > but I am still getting a Bad system call when I run a simple program > with and . What could I be doing wrong

Shared memory problem

I have followed the instructions in the README file and the messages already sent about this subject. The cygserver is set up and running, but I am still getting a Bad system call when I run a simple program with and . What could I be doing wrong? -- Unsubscribe info: http://cygwin.com

Memory Problem and X-windows

- Dear Cygwin Developers, With your help I have solved a problem of memory: MapViewOfFileEx(0x728, in_h 0x728) failed, Win32 error 6 I have used Wl,--stack,1 during link of my code written in Fortran and compiled with g77, but now there if another problem I can not get data into cod

Re: Memory Problem

At 07:27 AM 1/27/2005, you wrote: >- >Dear Cygwin Developers, > >I have a problem with running code which require High RAM Memory, >if I run this code in Windows Xp enviroment it runs, >if I use regular Redhat Linux also, but if I use Cygwin it produce message: > >MapViewOfFileEx(0x728, in_h 0x728

Memory Problem

- Dear Cygwin Developers, I have a problem with running code which require High RAM Memory, if I run this code in Windows Xp enviroment it runs, if I use regular Redhat Linux also, but if I use Cygwin it produce message: MapViewOfFileEx(0x728, in_h 0x728) failed, Win32 error 6 Code is in fortra