Memory Leak with Ruby 1.9.2 Rails 3.0 Beta 4

Furture info:

I try running the same Rails 3.0 Beta 4 application with Ruby Enterprise 1.8.7 and am not getting this same memory leak.

So Ruby 1.9.2 seems to be the problem, since it is leaking with both Rails 2.3.5 and Rails 3 Beta 4.

siege -c 1 http://localhost:3000

And wait one hour. Then wait another. Then wait another.

I use top from command prompt to view memory usage.

With Ruby Enterprise, I do not see any change in memory usage.

But with Ruby 1.9.2 memory keeps increasing. I have tried many Ruby 1.9.2 released in the recent months, including RC1. All had this problem.

I have this problem on Mac 10.6.3 and also Ubuntu 8.10.

All I have to do is

/opt/ruby/1.9.2/rails new example
cd example
/opt/ruby/1.9.2/rails server

then in another console I do

siege -c 1 http://localhost:3000

This happens in both development and production environment.

Even if I don't do siege, but keep hitting reload constantly on my browser pointing to http://localhost:3000 I will slowly achieve the same result.

Edited by Rohit Arondekar for formating.

I meant.

/opt/ruby/1.9.2/rails new example cd example
/opt/ruby/1.9.2/rails server

It should have been obvious though.

Well "cd example" is on a new line. Not sure why I don't get line break.

You can also indent it using four spaces, like this:

this is some code

Has anyone actually look at this?

I got this from a comment by Yehuda Katz in the Ruby forum:

This is something we're actively looking into. This is likely a problem in Ruby 1.9, but it may already be resolved (http:// redmine.ruby-lang.org/issues/show/3466#note-3). We're working with Aman Gupta (memprof), and have so far been unable to reproduce this issue. We are actively trying though.

source: http://www.ruby-forum.com/topic/213412#928210

Can you try it again with Ruby 1.9.2p0 or greater?

Any updates here?

I'm seeing a leak right now in a Rails 3.0.1 app on 1.9.2-p0. It happens on several views that poll a JSON-rendering action for status. The memory usage steadily climbs while the page is active, and does not release when the page is no longer active.