From: nobu@...
Date: 2015-02-28T00:47:34+00:00
Subject: [ruby-core:68345] [Ruby trunk - Bug #10913] [Third Party's Issue] Enum#each_slice is crashing with Bignum as an argument

Issue #10913 has been updated by Nobuyoshi Nakada.

Description updated
Status changed from Open to Third Party's Issue

It reproduces with just:

~~~ruby
Array.new(50000000000000000)
~~~

and

~~~ruby
"x"*50000000000000000
~~~

The failure itself is expected, but OSX's `malloc` complains.

Seems there is no hook to control it.

----------------------------------------
Bug #10913: Enum#each_slice is crashing with Bignum as an argument
https://bugs.ruby-lang.org/issues/10913#change-51691

* Author: arup rakshit
* Status: Third Party's Issue
* Priority: Normal
* Assignee: 
* ruby -v: ruby 2.1.2p95 (2014-05-08 revision 45877) [x86_64-darwin12.0]
* Backport: 2.0.0: UNKNOWN, 2.1: UNKNOWN, 2.2: UNKNOWN
----------------------------------------
~~~
[shreyas@~ (master)]$ rvm use 2.1.2
Using /Users/shreyas/.rvm/gems/ruby-2.1.2
[shreyas@~ (master)]$ pry
`[1] pry(main)> [1,2,3].each_slice(50000000000000000).to_a
pry(948,0x7fff73abb180) malloc: *** mmap(size=400000000000000000) failed (error code=12)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
pry(948,0x7fff73abb180) malloc: *** mmap(size=400000000000000000) failed (error code=12)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
NoMemoryError: failed to allocate memory
from (pry):1:in `each_slice'
[2] pry(main)>`
~~~



-- 
https://bugs.ruby-lang.org/