Public bug reported: Binary package hint: ruby1.9.1
I reported this, originally at #514322 I've put in another report as this affects Lucid as well as Karmic. This bug only seems to affect AMD64 platforms. The latest SVN trunk of Ruby 1.9 has been fixed for the last few weeks since it was marked as fixed at http://redmine.ruby- lang.org/issues/show/1392 A simple test case for this is under AMD64: ./ruby -e 'loop { Class.new.__send__ :include, Module.new }' ./ruby -e 'loop { Module.new.extend Module.new }' Running the above will leak memory. This is easy to see through any process listing application, such as top, or GNOME task manager. This will happen until the system runs out of memory, or the offending Ruby process is killed. Given that most people using Ruby 1.9.x will be Rails developers using Rails in development (debug) mode who wish to migrate their code base from 1.8.x so it's compatible with 1.9.x, I would guess that it is in the interest in the Ruby & Rails community to utilize the latest 1.9.x branch were possible. Also, given that in the Ruby community that Ruby 1.9 is known to be a moving target, developers will want to test against the latest version (compared to 1.8.x which is supposed to fairly static and thus considered stable). Will it be asking too much to do this, (as I'm guessing the packages are pulled upstream from Debian, I'm guessing this will need to be passed on to Debian maintainers?) ** Affects: ruby1.9.1 (Ubuntu) Importance: Undecided Status: New -- Ruby 1.9.1 leaks memory in Lucid on AMD64 https://bugs.launchpad.net/bugs/529011 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
