From: "jshow (Jodi Showers)" <jodi@...>
Date: 2012-04-24T02:14:01+09:00
Subject: [ruby-core:44563] [ruby-trunk - Bug #6246] 1.9.3-p125 intermittent segfault


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


Yusuke Endoh, 

I have tried your example, but unfortunately couldn't cause a crash. I experimented with various values of as high as 3000.

I would appreciate whatever effort can be applied - I am literally stuck as 125 crashes so often it's unusable.

If I can provide more details I would be happy to do so

OT, but I don't receive any emails from redmine - I'm watching this issue, and have the general mail settings turned on. Hard to follow - I presently come back to visit regularly.

thanks.


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

Author: jshow (Jodi Showers)
Status: Assigned
Priority: Normal
Assignee: authorNari (Narihiro Nakamura)
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/