Issue #6246 has been updated by jshow (Jodi Showers).


Aaron, I've updated this gist with a run that uses a more direct command line - which I think was hiding some of the valgrind output

valgrind --num-callers=50 --error-limit=no --partial-loads-ok=yes --undef-value-errors=no rake RAILS_ENV=new_staging assets:precompile

https://gist.github.com/2296847

still it seems we're not getting much value from valgrind - it's reporting 0 errors from 0 contexts

I'm re-running now with -v and --leak-check=full for more

----------------------------------------
Bug #6246: 1.9.3-p125 intermittent segfault
https://bugs.ruby-lang.org/issues/6246#change-25656

Author: jshow (Jodi Showers)
Status: Open
Priority: Normal
Assignee: 
Category: 
Target version: 
ruby -v: ruby 1.9.3p125 (2012-02-16 revision 34643) [x86_64-linux]


I've seen this behavior in 1.9.3p0 and 1.9.3p125

Intermittently, a rails 3.2 rake task will break while compiling assets - about 1 in 10 runs will segfault. Our code is 10K's of lines of proprietary code. I am working on a simplified version you can use.

RAILS_ENV=new_staging bundle exec rake assets:precompile --trace

command: https://gist.github.com/2254457 (stacktrace and gem list)

backtrace : https://gist.github.com/2286260

Operating System : Debian Squeeze 6.0.4
Ruby installed through RVM 1.11.3




-- 
http://bugs.ruby-lang.org/