MRI out of memory (or segfault) when trying to compare controller response with Fixnum

[fdutey]

After couple of minutes (around 10), Ruby VM is not able to allocate memory. Sometimes segfault...

My mistake is response.should == 401 instead of response.status.should == 401 but still, I think it shouldn't kill Ruby VM

code:

  it '...' do
    get :index, :line_item_id => @line_item.id, :format => :json

    response.should == 401
  end

gems:

rspec (2.11.0)
rspec-core (2.11.1)
rspec-expectations (2.11.3)
rspec-mocks (2.11.3)
rspec-rails (2.11.0)
shoulda-matchers (1.4.2)

[myronmarston]

This is a bug in rack that is solved on newer rack versions. For more info, see the following issues:

• [response].flatten causes infinite loop rack/rack#419
• RSpec raises OutOfMemoryError rspec-expectations#166
• 100% CPU when comparing ActiveController::TestResponse with a primitive rspec-rails#601
• Controller specs: response.should == 'string' rspec-rails#613
• `expect(response).to_eq('something') hangs if it's a redirect rspec-rails#667

[sdhull]

FWIW I don't think the fix in rack is available from RubyGems yet.