Re: [Rails] Stack Level Too Deep Error (can't seem to figure it out)

On 17 December 2011 07:40, Vell <lovell.mcilwain@gmail.com> wrote:
> Hi all,
>
> I am running into a weird issue where my application is giving me a
> stack level too deep error. I can't seem to find where my code is
> throwing this error. On the machine I developed this code on, this
> error does not show up  when I run rails s but when I move the code to
> another system to run it this error shows up.
>
> The system that this code runs fine on is a mac os x machine running
> lion with rvm (ruby 1.9.2), rails 3.0.10.
>
> The system that is giving me this error it is a ubuntu 10.11 using
> passenger 3.0.11, apache2, rvm (ruby 1.9.2) and rails 3.0.10.
>
> When I create a vanilla rails app on the ubuntu system, this error
> does not show.
>
> When I hit my application from the web, no matter which view I hit I
> get the following error:
>
> Showing /home/rails30/apps/vell/app/views/homes/index.html.erb where
> line # raised:
>
> stack level too deep
>
> Extracted source (around line #):
>
> Rails.root: /home/rails30/apps/vell
> Application Trace | Framework Trace | Full Trace
>
> activesupport (3.0.10) lib/active_support/core_ext/class/attribute.rb:
> 81
>
> the development log shows:
>
> Completed 500 Internal Server Error in 282ms
>
> ActionView::Template::Error (stack level too deep):
>
>
> Rendered /home/vmcilwain/.rvm/gems/ruby-1.9.2-p290/gems/
> actionpack-3.0.10/lib/action_dispatch/middleware/templates/rescues/
> _trace.erb (1.9ms)
> Rendered /home/vmcilwain/.rvm/gems/ruby-1.9.2-p290/gems/
> actionpack-3.0.10/lib/action_dispatch/middleware/templates/rescues/
> _request_and_response.erb (93.8ms)
> Rendered /home/vmcilwain/.rvm/gems/ruby-1.9.2-p290/gems/
> actionpack-3.0.10/lib/action_dispatch/middleware/templates/rescues/
> template_error.erb within rescues/layout (107.0ms)
>
> Anyone have any ideas on how I can figure out what is causing this
> error? I have tried poking around but Im afraid I just can't seem to
> find it.

I don't have a specific solution, but you could try using the Gemfile
from the failing app with your vanilla app so that the same gems are
used. If that breaks the vanilla app then you can find the gem that
causes the problem.

Colin

--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To unsubscribe from this group, send email to rubyonrails-talk+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.