Databases
StackOverflow2013
Postsdbo
POSystemStackError triggered by changing files while server is running?
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSystemStackError triggered by changing files while server is running?
    text
    copied!<p>On my RoR app development machine (local server, OSX 10.8.1, Ruby 1.9.3, Rails 3.2.8) something odd started to appear out of thin air (of course…):</p> <p>The Rails server collapses (all routes are killed, server restart is the only way to get it working again) with the following log entries:</p> <pre><code>SystemStackError (stack level too deep): actionpack (3.2.8) lib/action_dispatch/middleware/reloader.rb:70 Rendered /Users/dekay/.rvm/gems/ruby-1.9.3-head@global/gems/actionpack-3.2.8/lib/action_dispatch/middleware/templates/rescues/_trace.erb (1.9ms) Rendered /Users/dekay/.rvm/gems/ruby-1.9.3-head@global/gems/actionpack-3.2.8/lib/action_dispatch/middleware/templates/rescues/_request_and_response.erb (1.2ms) Rendered /Users/dekay/.rvm/gems/ruby-1.9.3-head@global/gems/actionpack-3.2.8/lib/action_dispatch/middleware/templates/rescues/diagnostics.erb within rescues/layout (14.7ms) </code></pre> <p>I have googled and found that the SystemStackError is usually due to an endless loop, but as far as I can trace it I have no such loop in my code. And the error does not seem to be in a certain step of application logic.</p> <p>The only correlation between server crash and my actions is as follows:</p> <ol> <li>Change some code in the app</li> <li>Reload the current web page of the app</li> <li>Boom, server gone, error message. </li> <li><p>No pages work after this, error is:</p> <p>Routing Error</p> <p>No route matches [GET] "/"</p> <p>Try running rake routes for more information on available routes.</p></li> </ol> <p>Can anyone point me in the right direction to debug this, please? PS: I suspect it happened after a careless "bundle update". Can this be?</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload