Although Ruby 1.8.7 is not officially recommended yet for Ruby on Rails, it does in fact work fine with Rails 2.1. And version p22 contains all the latest security fixes.For what it’s worth, I can confirm that not only are our apps working well under 1.8.7 (including ferret and over 30,000 lines of app code), but they are consuming / leaking considerably less memory. (They still do leak, but the rate is much reduced.)So upgrade now.Beware of one issue – we had to clean up our ERB code to not contain comments that are not specifically marked inside their own tags like <%# comment %> because of different handling in 1.8.7.
- Comment
- Reblog
-
Subscribe
Subscribed
Already have a WordPress.com account? Log in now.
Pennysmalls 
might be nice to run it under valgrind and see where it’s still leaking, if anywhere.-R
It would be good if a version of 1.8.7 could be made for running with valgrind.Anyone fancy porting / testing Evan’s patches with 1.8.7? http://blog.evanweaver.com/articles/2008/02/05/valgrind-and-ruby/
For me if I just ran valgrind and 1.8.6 it spit out a few errors during parsing, but I just ignored those and then look for ‘lost memory’ reports at the end or scanned through for errors that looked related to my own code. I never even used evan’s patch. I guess that might help clean things up 🙂
rQYDFU <a href="http://kbvmrxzuvfqy.com/" rel="nofollow">kbvmrxzuvfqy</a>, [url=http://tfvbgtgkxkqi.com/]tfvbgtgkxkqi[/url], [link=http://ehvjetwshgyo.com/]ehvjetwshgyo[/link], http://jxxagxcbsnss.com/%5BWORDPRESS HASHCASH] The poster sent us ‘0 which is not a hashcash value.
http://www.idle-hacking.com/2008/07/valgrind-ruby-187-updated-patchmight work