This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: crash - cygheap - longjmp


my max paging file size is 1.5GByte.

While I was running the offending script, I was watching the current paging 
file size in the task manager.
It is rock-solid at around 590MByte and doesn't even change when the script 
barfs as I'd described in my orig. posting!

Insufficient paging file size must be ruled out.

Also tried latest snapshot.
Script barfs after running it four times - then reboot is in order.


Brian Dessent wrote:
> Hans Horn wrote:
>> c:\cygwin\bin\bash.exe (1104): *** couldn't map space for new
>> cygheap, Win32 error 1455
> $ net helpmsg 1455
> The paging file is too small for this operation to complete.
>> c:\cygwin\bin\bash.exe (4060): *** couldn't create signal pipe,
>> Win32 error 1816
> $ net helpmsg 1816
> Not enough quota is available to process this command.
>> After that nothing helps but rebooting the machine.
> You may simply be running out of page file, so try increasing its
> size.
> Alternatively, this sort of thing seems to happen when there is some
> kind of memory leak caused by third party software, usually stuff that
> is related to networking.  Someone else recently found that their VPN
> client was causing similar "Resource not available" errors during a
> large build process.  A lot of these types of software install
> themselves as shims into the winsock stack, and apparently leak
> handles or memory badly in certain circumstances.
> You should also try the latest Cygwin snapshot.
> Brian 

Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]