I get the following error running CygWin find and xargs from within a TCL script:
Error executing 'C:/cygwin/bin/find TempDir/QACData -name *.lock -type f
-print0 | xargs -0r rm -r'...
c:\cygwin\bin\xargs.exe: *** unable to allocate heap, heap_chunk_size
384, Win32 error 0
The error is intermittent and I haven't been able to reproduce it outside
the TCL script (whether from bash, cmd, tclsh, whatever).
There's similar prior art in the archives, but this one has the crucial
difference that the reported heap_chunk_size is small but non-zero.
I've had a look through the relevant source (shared.cc, heap.cc), and my
initial thought was that shared_info::heap_chunk_size() was returning a
rogue size for some reason. It seems that the memory-zeroing behaviour of
Win32 CreateFileMapping() is used to initialise shared_info::heap_chunk to
zero. Is CreateFileMapping() completely trustworthy in this respect?
cygcheck.out
Description: Binary data
-- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
