Re: proc extension problems

Maksym Melnychok
Fri, 23 Mar 2012 11:12:06 -0000

yeah, i saw that. i actually found why exactly this problem happens - new
symbol is generated every time a named scope is called which was defined on
ActiveRecord::Base

On Thursday, March 22, 2012 3:39:11 PM UTC+1, Sky Faber
wrote:
>
> This seems like a known problem with ruby.
>
> I found this old discussion of the issue back from 2008.
>
>
http://www.ruby-forum.com/​topic/173699<http://www.ruby-forum.com/topic/173699>
>
> -Sky
> On Mar 22, 2012 4:00 AM, "Maksym Melnychok"
<keymone@gmail.com> wrote:
>
>> Hi guys,
>>
>> has anyone had problems with this bit of code: https://github.com/**
>> rails​/rails/blob/master/**activesuppo​rt/lib/active_**
>>
support/core_​ext/proc.rb<https://github.com/rails/rails/blob/master/activesupport/lib/active_support/core_ext/proc.rb>
>>  ?
>>
>> if i run my application for long enough time i start getting errors
like
>> this:
>>
>> RuntimeError: symbol table overflow (symbol __bind_1328993330_18...)
>>
>> apparently it''s because symbols are never GCed and rails
generates one
>> every time this proc extension is used because method names are
implicitly
>> converted to symbols
>>
>> Best Regards,
>> MM
>>
>> --
>> 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/-/​mys8W5xHmsUJ<https://groups.google.com/d/msg/rubyonrails-core/-/mys8W5xHmsUJ>
>> .
>> To post to this group, send email to
rubyonrails-core@googlegroups.​com<rubyonrails-core@googlegroups.com>
>> .
>> To unsubscribe from this group, send email to
>>
rubyonrails-core+unsubscribe@​googlegroups.com<rubyonrails-core%2Bunsubscribe@googlegroups.com>
>> .
>> For more options, visit this group at
>>
http://groups.google.com/​group/rubyonrails-core?hl=en<http://groups.google.com/group/rubyonrails-core?hl=en>
>> .
>>
>

--
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