4 ms·
I can't post the actual backtrace, but looking at the most recent error email I received from a Rails app, the backtrace is over 300 calls deep. 50 New Relic,
by agf 10y ago
I can't post the actual backtrace, but looking at the most recent error email I received from a Rails app, the backtrace is over 300 calls deep.
50 New Relic, 50 ActiveRecord, 100 ActiveSupport, 50 misc Rails / Rack, and 50 everything else.
This is not a Java problem.
- BillinghamJ 10y agoYup, the issue with Java and Ruby is not the languages, but the people using them.
- bazzargh 10y agoRails comes with a backtrace cleaner, that by default excludes lines that aren't from your app; it's based on an extensible BacktraceCleaner in ActiveSupport. https://github.com/rails/rails/blob/master/railties/lib/rails/backtrace_cleaner.rb https://github.com/rails/rails/blob/master/railties/lib/rail... Perhaps you've disabled this? (FWIW, I don't mind the longer backtraces as they help in understanding thornier problems.)
- agf 10y agoYeah, we definitely need the full backtraces as we've significantly customized rails so seeing the full call stack is important. It's not seeing a long backtrace that bothers me, it's the callstack being that deep to begin with. In my experience, it makes debugging slower and more difficult. If you're 30 calls deep, figuring out where you ended up in the wrong branch of a conditional is much easier than when you're 300 calls deep.