1.7.7-1: troubleshooting "couldn't allocate heap, Win32 error 487" [resolved]

Casey Boettcher cboettcher@gmail.com
Sun Oct 10 21:31:00 GMT 2010

On Sun, Oct 10, 2010 at 12:50, Casey Boettcher <cboettcher@gmail.com> wrote:
>> ---------- Forwarded message ----------
>> From: Marco Atzeri <marco>
>> To: cygwin <cygwin>, Ken Brown <kbrown>
>> Date: Sun, 10 Oct 2010 12:28:24 +0100 (BST)
>> Subject: Re: 1.7.7-1: troubleshooting "couldn't allocate heap, Win32 error 487"
>> --- Dom 10/10/10, Ken Brown ha scritto:
>>> On 10/10/2010 3:49 AM, Casey
>>> Boettcher wrote:
>>> > Hello,
>>> >
>>> > I'm attempting to troubleshoot a problem that occurs
>>> when I boot
>>> > Windows 7 normally, but does not occur when I boot
>>> into Safe Mode.
>>> >
>>> > The problem is this: when I run cygwin.bat, I receive
>>> the following
>>> > within the console (excerpted here, but full output is
>>> attached in
>>> > bash.out):
>>> >
>>> > -----
>>> >        2 [main] bash 1264
>>> C:\cygwin\bin\bash.exe: *** fatal error -
>>> > couldn't allocate heap, Win32 error 487, base
>>> 0xA40000, top 0xA90000,
>>> > reserve_size 323584, allocsize 327680, page_const
>>> 4096
>>> [...]
>>> > I've attached output from "cygcheck -r -s -v" as
>>> instructed on
>>> > http://www.cygwin.com/problems.html
>>>  From your cygcheck output:
>>>    Warning: There are multiple cygwin1.dlls
>>> on your path
>>> Ken
>> .\cygwin1.dll
>> and
>> C:\cygwin\bin\cygwin1.dll
>> are likely the same file, so it could be a bogus warning
>> Any chance of "Logitech Quick Camera driver" installed ?
>> Marco
> Ken and Marco,
> Thanks for your responses. I'm pretty sure the duplicate DLL warning
> is superfluous, as both paths point to the same file.
> As far as a Logitech camera driver is concerned: I have a camera
> driver, and I have Logitech devices, but I have no Logitech camera.
> I avoided troubleshooting loaded drivers (even though that tack would seem
>  to be obvious given my success in Safe Mode) because I've no idea how
> to go about doing it. I've unplugged all of my peripherals and
> rebooted, but that had no effect.
> Any advice on the best way to isolate a problematic driver on a
> Windows 7 system? Is there a way to "dynamically" load and unload
> drivers from the
> system without rebooting?
> Regards,
> Casey

I downloaded windbg and selected File->Open Executable..., specifying
"bash.exe," "--login -i" as arguments and "C:\cgywin\bin" as the
working directory. This is what initially appeared in the debugging

CommandLine: C:\cygwin\bin\bash.exe --login -i
Starting directory: C:\cygwin\bin
Symbol search path is: *** Invalid ***
* Symbol loading may be unreliable without a symbol search path.           *
* Use .symfix to have the debugger choose a symbol path.                   *
* After setting your symbol path, use .reload to refresh symbol locations. *
Executable search path is:
ModLoad: 00000000`00400000 00000000`0047d000   image00000000`00400000
ModLoad: 00000000`772b0000 00000000`7745b000   ntdll.dll
ModLoad: 00000000`77490000 00000000`77610000   ntdll32.dll
ModLoad: 00000000`74f90000 00000000`74fcf000   C:\Windows\SYSTEM32\wow64.dll
ModLoad: 00000000`74f30000 00000000`74f8c000   C:\Windows\SYSTEM32\wow64win.dll
ModLoad: 00000000`74f20000 00000000`74f28000   C:\Windows\SYSTEM32\wow64cpu.dll
(44c.804): Break instruction exception - code 80000003 (first chance)
*** ERROR: Symbol file could not be found.  Defaulted to export
symbols for ntdll.dll -
00000000`77361340 cc              int     3

After continuing execution, the following was displayed:

0:000> g
ModLoad: 00000000`77090000 00000000`771af000   WOW64_IMAGE_SECTION
ModLoad: 00000000`75060000 00000000`75160000   WOW64_IMAGE_SECTION
ModLoad: 00000000`77090000 00000000`771af000   NOT_AN_IMAGE
ModLoad: 00000000`771b0000 00000000`772aa000   NOT_AN_IMAGE
ModLoad: 00000000`75060000 00000000`75160000   C:\Windows\syswow64\kernel32.dll
ModLoad: 00000000`75260000 00000000`752a6000
ModLoad: 00000000`6fc00000 00000000`6fc10000   C:\cygwin\bin\cyggcc_s-1.dll
ModLoad: 00000000`61000000 00000000`61300000   C:\cygwin\bin\cygwin1.dll
ModLoad: 00000000`75370000 00000000`75410000   C:\Windows\syswow64\ADVAPI32.DLL
ModLoad: 00000000`76740000 00000000`767ec000   C:\Windows\syswow64\msvcrt.dll
ModLoad: 00000000`767f0000 00000000`76809000   C:\Windows\SysWOW64\sechost.dll
ModLoad: 00000000`75410000 00000000`75500000   C:\Windows\syswow64\RPCRT4.dll
ModLoad: 00000000`75000000 00000000`75060000   C:\Windows\syswow64\SspiCli.dll
ModLoad: 00000000`74ff0000 00000000`74ffc000   C:\Windows\syswow64\CRYPTBASE.dll
ModLoad: 00000000`6fa10000 00000000`6fa1d000   C:\cygwin\bin\cygintl-8.dll
ModLoad: 00000000`6fa30000 00000000`6fb2b000   C:\cygwin\bin\cygiconv-2.dll
ModLoad: 00000000`72c30000 00000000`72c5e000   C:\cygwin\bin\cygreadline7.dll
ModLoad: 00000000`6f730000 00000000`6f766000   C:\cygwin\bin\cygncurses-9.dll
ModLoad: 00000000`75160000 00000000`75260000   C:\Windows\syswow64\USER32.dll
ModLoad: 00000000`76a50000 00000000`76ae0000   C:\Windows\syswow64\GDI32.dll
ModLoad: 00000000`75510000 00000000`7551a000   C:\Windows\syswow64\LPK.dll
ModLoad: 00000000`75520000 00000000`755bd000   C:\Windows\syswow64\USP10.dll
(44c.804): WOW64 breakpoint - code 4000001f (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
*** ERROR: Symbol file could not be found.  Defaulted to export
symbols for ntdll32.dll -
77530995 cc              int     3

Nothing of note yet in the cmd window, so I restart execution and get
the following in the debugger. The cmd window is now full of stack
trace identical to that contained in the attachment I posted at the
beginning of this thread:

0:000:x86> g
cYgFFFFFFFF 61177B80ModLoad: 00000000`76c40000 00000000`76ca0000
ModLoad: 00000000`76fc0000 00000000`7708c000   C:\Windows\syswow64\MSCTF.dll
ModLoad: 00000000`74ec0000 00000000`74eed000
ModLoad: 00000000`755c0000 00000000`76209000   C:\Windows\syswow64\SHELL32.dll
ModLoad: 00000000`752b0000 00000000`75307000   C:\Windows\syswow64\SHLWAPI.dll
ModLoad: 00000000`74eb0000 00000000`74eb9000   C:\Windows\SysWOW64\VERSION.dll
ModLoad: 00000000`74e70000 00000000`74ea2000   C:\Windows\SysWOW64\WINMM.dll
ModLoad: 00000000`76ae0000 00000000`76c3c000   C:\Windows\syswow64\ole32.dll
cYgstd 28cce5 d 3ModLoad: 00000000`1a500000 00000000`1a600000
ModLoad: 00000000`74e40000 00000000`74e61000   C:\Windows\SysWOW64\ntmarta.dll
ModLoad: 00000000`76e70000 00000000`76eb5000   C:\Windows\syswow64\WLDAP32.dll
ModLoad: 00000000`76a10000 00000000`76a45000   C:\Windows\SysWOW64\ws2_32.dll
ModLoad: 00000000`76730000 00000000`76736000   C:\Windows\syswow64\NSI.dll
ModLoad: 00000000`74e30000 00000000`74e40000   C:\Windows\SysWOW64\NLAapi.dll
ModLoad: 00000000`74df0000 00000000`74e2c000   C:\Windows\SysWOW64\mswsock.dll
ModLoad: 00000000`74da0000 00000000`74de4000   C:\Windows\SysWOW64\DNSAPI.dll
ModLoad: 00000000`74d90000 00000000`74d98000   C:\Windows\SysWOW64\winrnr.dll
ModLoad: 00000000`74d80000 00000000`74d90000   C:\Windows\SysWOW64\napinsp.dll
ModLoad: 00000000`74d60000 00000000`74d72000   C:\Windows\SysWOW64\pnrpnsp.dll
ModLoad: 00000000`74d30000 00000000`74d55000   C:\Program Files
ModLoad: 00000000`74d10000 00000000`74d2c000   C:\Windows\SysWOW64\Iphlpapi.DLL
ModLoad: 00000000`74d00000 00000000`74d07000   C:\Windows\SysWOW64\WINNSI.DLL
ModLoad: 00000000`74cc0000 00000000`74cf6000   C:\Windows\SysWOW64\Audioses.dll
ModLoad: 00000000`76980000 00000000`76a0f000   C:\Windows\syswow64\OLEAUT32.dll
ModLoad: 00000000`74c80000 00000000`74cb9000   C:\Windows\SysWOW64\MMDevAPI.DLL
ModLoad: 00000000`74b80000 00000000`74c75000   C:\Windows\SysWOW64\PROPSYS.dll
ModLoad: 00000000`74b30000 00000000`74b7b000   C:\Windows\SysWOW64\apphelp.dll

Looking at the list, a few DLLs stand out as being likely candidates
(namely, those not produced by Microsoft). After uninstalling
AudioFoil (an application that allows for streaming audio to an Apple
AirPort Express), my problems were solved.

Thanks again for your assistance and to the Cygwin team for a
wonderful application.


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

More information about the Cygwin mailing list