SystemStackError (stack level too deep) when creating new AR

Rails
1

Hi. I have a problem with very deep calls, causing SystemStackError.

The logs are on Parked at Loopia

It scares me, because I don’t understand it’s cause, and I fear it may
strike on production (in case it disappears in development :wink: )

Tests are passing without disturbance.
Maybe it’s because of webrick, as it creates almost half of the
call-trace?
I plan to use fastcgi later.

2

I got this odd error when using the console, however a restart of the
console fixes it. Any thoughts?

Note that the stack level is only like 20 deep, and I have tested it and
it can go (typically) to thousands deep. So something must be using up
tons of stack space?

exceptionstack level too deepSystemStackError: stack level too deep
from
/opt/local/lib/ruby/gems/1.8/gems/activerecord-1.15.3/lib/active_record/base.rb:1983:in
==' from /opt/local/lib/ruby/gems/1.8/gems/activerecord-1.15.3/lib/active_record/base.rb:1983:in ===’
from
/opt/local/lib/ruby/gems/1.8/gems/activerecord-1.15.3/lib/active_record/base.rb:1983:in
convert_number_column_value' from /opt/local/lib/ruby/gems/1.8/gems/activerecord-1.15.3/lib/active_record/base.rb:1973:in write_attribute’
from
/opt/local/lib/ruby/gems/1.8/gems/activerecord-1.15.3/lib/active_record/attribute_methods.rb:67:in
attribute=' from /opt/local/lib/ruby/gems/1.8/gems/activerecord-1.15.3/lib/active_record/base.rb:1855:in send’
from
/opt/local/lib/ruby/gems/1.8/gems/activerecord-1.15.3/lib/active_record/base.rb:1855:in
method_missing' from /opt/local/lib/ruby/gems/1.8/gems/activerecord-1.15.3/lib/active_record/base.rb:1672:in send’
from
/opt/local/lib/ruby/gems/1.8/gems/activerecord-1.15.3/lib/active_record/base.rb:1672:in
attributes=' from /opt/local/lib/ruby/gems/1.8/gems/activerecord-1.15.3/lib/active_record/base.rb:1671:in each’
from
/opt/local/lib/ruby/gems/1.8/gems/activerecord-1.15.3/lib/active_record/base.rb:1671:in
attributes=' from /opt/local/lib/ruby/gems/1.8/gems/activerecord-1.15.3/lib/active_record/base.rb:1505:in initialize_without_callbacks’
from
/opt/local/lib/ruby/gems/1.8/gems/activerecord-1.15.3/lib/active_record/callbacks.rb:225:in
initialize' from /opt/local/lib/ruby/gems/1.8/gems/activerecord-1.15.3/lib/active_record/base.rb:449:in new’
from
/opt/local/lib/ruby/gems/1.8/gems/activerecord-1.15.3/lib/active_record/base.rb:449:in
create' from ./db/add_multiple_zips.rb:425 from ./db/add_multiple_zips.rb:415:in each_line’
from ./db/add_multiple_zips.rb:415
from ./db/add_multiple_zips.rb:400:in each' from ./db/add_multiple_zips.rb:400 from /opt/local/lib/ruby/gems/1.8/gems/activesupport-1.4.2/lib/active_support/dependencies.rb:493:in load’
from
/opt/local/lib/ruby/gems/1.8/gems/activesupport-1.4.2/lib/active_support/dependencies.rb:493:in
load' from /opt/local/lib/ruby/gems/1.8/gems/activesupport-1.4.2/lib/active_support/dependencies.rb:345:in new_constants_in’
from
/opt/local/lib/ruby/gems/1.8/gems/activesupport-1.4.2/lib/active_support/dependencies.rb:493:in
`load’
from (irb):25>>

Arsen7 wrote:

Hi. I have a problem with very deep calls, causing SystemStackError.

The logs are on Parked at Loopia

It scares me, because I don’t understand it’s cause, and I fear it may
strike on production (in case it disappears in development :wink: )

Tests are passing without disturbance.
Maybe it’s because of webrick, as it creates almost half of the
call-trace?
I plan to use fastcgi later.