The bug report specifies what is causing the over-allocation and how to fix it. It's pretty specific.
On Thursday, September 13, 2012 12:39:23 PM UTC-7, Steve Klabnik wrote: > > Adding issues does not help, and only creates noise on the tracker. > > Specifics about WHAT is causing over-allocation or HOW to fix it may be > valid. But an open issue for 'tons 'o objects' helps nobody and is not > productive. It is far too general. > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To view this discussion on the web visit https://groups.google.com/d/msg/rubyonrails-core/-/k0qxw-y377QJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
