A few weeks ago I updated my development computer to Snow Leopard (finally). I put it off because I was in the middle of a project, and it seems its a good thing I did. Last week I started something new and it seems that any rails related ruby process will get ... stuck, I guess is the best word. I've seen it happen as soon as a minute, or take as long as an hour. It happens for script/server and script/ runner based processes; as far as I've been able to tell, it doesn't happen with pure ruby processes, but then again the test script I used wasn't trying to do things like connect to a MySQL DB. When the processes get stuck, control-c does not stop them, they have to be forced to quit with "kill -9".
Has anyone else seen this? Thanks! Mark Some info from my environment... > ruby --version ruby 1.8.7 (2010-01-10 patchlevel 249) [i686-darwin10.2.0] > env | grep RUBY RUBYOPT=rubygems > mysql --version mysql Ver 14.14 Distrib 5.1.44, for apple-darwin10.2.0 (i386) using readline 5.1 > gem list --local actionmailer (2.3.5, 2.1.1) actionpack (2.3.5, 2.1.1) activerecord (2.3.5, 2.1.1) activeresource (2.3.5, 2.1.1) activesupport (2.3.5, 2.1.1) ... mongrel (1.1.5) mysql (2.8.1) ... rails (2.3.5, 2.1.1) rake (0.8.7, 0.8.3) ... rubyforge (2.0.3, 1.0.1) rubygems-update (1.3.6, 1.3.5) ... > gem --version 1.3.6 -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
