Rails on Ruby 1.8.7

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.

4 comments for this post.

  1. Comment from roger degree search | 3 July 2008 | 7:47 pm :

    might be nice to run it under valgrind and see where it’s still leaking, if anywhere.
    -R

  2. Comment from Stephen Sykes | 4 July 2008 | 8:10 am :

    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/

  3. Comment from roger accredited degrees | 8 July 2008 | 4:22 pm :

    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 :)

  4. Comment from roger | 26 August 2008 | 9:15 pm :

    http://www.idle-hacking.com/2008/07/valgrind-ruby-187-updated-patch
    might work

Leave your comment...

Powered by WP Hashcash

Blog Archives

Navigation


About this blog

A blog about Ruby, Rails and other tech. Mostly.


Find Something?