Skip to content

Instantly share code, notes, and snippets.

@eduardordm
Created June 22, 2011 17:52
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save eduardordm/1040673 to your computer and use it in GitHub Desktop.
Save eduardordm/1040673 to your computer and use it in GitHub Desktop.
REALLY??!??!?!
Started GET "/assets/application.js" for 127.0.0.1 at 2011-06-22 13:51:25 -0400
Compiled ~/Intermeta/smsy/app/assets/javascripts/application.js (3ms) (pid 60381)
Compiled ~/.rvm/gems/ruby-1.9.2-p180@rails31rc4/gems/jquery-rails-1.0.11/vendor/assets/javascripts/jquery.js (1ms) (pid 60381)
Compiled ~/.rvm/gems/ruby-1.9.2-p180@rails31rc4/gems/jquery-rails-1.0.11/vendor/assets/javascripts/jquery_ujs.js (0ms) (pid 60381)
Compiled ~/Intermeta/smsy/app/assets/javascripts/posts.js.coffee (80ms) (pid 60381)
Compiled ~/Intermeta/smsy/app/assets/javascripts/welcome.js.coffee (0ms) (pid 60381)
Served asset /application.js - 304 Not Modified (91ms) (pid 60381)
/Users/eduardo/.rvm/gems/ruby-1.9.2-p180@rails31rc4/gems/sass-3.1.2/lib/sass/util.rb:510: [BUG] Segmentation fault
ruby 1.9.2p180 (2011-02-18 revision 30909) [x86_64-darwin10.7.0]
@cowboyd
Copy link

cowboyd commented Jun 22, 2011

This issue is caused by an old version of therubyracer which did not play well running in multithreaded environments. see:

http://blog.thefrontside.net/2011/06/13/therubyracer-isnt-threadsafe-yet/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment