Hi,

"Bill Kelly" <billk / cts.com> writes:

:> Why did Ruby fail at 265 megs and is there another way for me to do this?
:
:Interesting, I tried it under ruby 1.6.2 (2000-12-18) [i386-cygwin]
:and got a failure at the same point (~265 megs), but instead of an
:out-of-memory error, I got:
:
:  /cygdrive/t/test.rb:5: [BUG] Segmentation fault
:  ruby 1.6.2 (2000-12-18) [i386-cygwin]
:        0 [sig] ruby 1336 open_stackdumpfile: Dumping stack trace to
:  ruby.exe.stackdump
:
:Whereas under ruby 1.6.6 (2001-12-26) [i586-mswin32], the script
:worked, allocating well over 300M, and completing successfully.
:
:That [i586-mswin32] version also completed the task about 20x faster
:than the cygwin version. . . . My cygwin1.dll is 1003.2.0.0.
:
:It would seem cygwin's memory allocation may be subtly broken?

$ regtool -i set '\user\SOFTWARE\Cygnus Solutions\Cygwin\heap_chunk_in_mb' 512

The default heap_chunk_in_mb is 256MB.
For more details check the cygwin ML:
  http://cygwin.com/ml/cygwin/

-- 
eban