Your attachments are missing. :)
But if it's the Ruby process crashing then there's nothing Phusion Passenger can do about it. Most likely it's a bug in Ruby 2.0. In our tests we've also found a number of Ruby 2.0 bugs that indicate it's better to wait for the next patchlevel.
Sent from my Android phone.
I'm getting a random segmentation fault when running Passenger 4.0.0-rc4 on Ruby 2.0.0. I can reproduce the problem by loading the same page 3 - 20 times - eventually I'll get a segmentation fault. I've tried both Apache and Nginx and both suffer from the problem, so it's obviously not web server issue. It doesn't coincide with any particular library. Sometimes it'll bomb out in ERB while processing a template, sometimes in SASS, sometimes in Nokogiri, etc. I've managed to work around the problem by setting the spawn method to direct rather than smart, but I'd really like to make using of smart spawning if possible. It's obviously a threading problem, but have no idea at what level: Ruby, Passenger, or some other library.Does anyone know what I should do to try and get to the bottom of what's causing this? I've attached a dump of the passenger debug log file containing numerous segmentation faults.
--
You received this message because you are subscribed to the Google Groups "Phusion Passenger Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to phusion-passen...@googlegroups.com.
To post to this group, send email to phusion-...@googlegroups.com.
Visit this group at http://groups.google.com/group/phusion-passenger?hl=en-US.
For more options, visit https://groups.google.com/groups/opt_out.