Rails Ruby on Rails → 3.0.2

Comments and changes to this ticket

• You flagged this item as spam.
  

  drjoke July 4th, 2010 @ 11:56 AM

  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.

• 

  Rohit Arondekar July 4th, 2010 @ 12:24 PM

  • Tag set to “memory leak, ruby1.9.2”
  • Importance changed from “” to “Low”

  Can you provide some more information like which version of siege, operating system and some kind of log output that shows the memory leak? Also if you ran siege with a particular configuration. It would help those trying to reproduce the problem.

• You flagged this item as spam.
  

  drjoke July 4th, 2010 @ 01:51 PM

  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.

• You flagged this item as spam.
  

  drjoke July 4th, 2010 @ 01:53 PM

  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.

• You flagged this item as spam.
  

  drjoke July 4th, 2010 @ 01:54 PM

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

• 

  José Valim July 4th, 2010 @ 01:54 PM

  • Milestone cleared.
  • Importance changed from “Low” to “High”
• 

  Rohit Arondekar July 4th, 2010 @ 02:01 PM

  • State changed from “new” to “open”

  Moodang, thank you for reporting the issue. :)

  P.S fixed formating in your comment, wrapping console commands & code in @@@ is the way to go. Take a look at http://help.lighthouseapp.com/faqs/getting-started/how-do-i-format-... for details.

• 

  Ryan Bigg July 26th, 2010 @ 02:16 AM

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

  this is some code
  

• You flagged this item as spam.
  

  drjoke July 26th, 2010 @ 04:13 AM

  Has anyone actually look at this?

• 

  Rohit Arondekar July 26th, 2010 @ 06:58 AM

  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

• You flagged this item as spam.
  

  Preston Marshall August 23rd, 2010 @ 08:21 AM

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

• 

  Jeremy Kemper August 30th, 2010 @ 04:10 AM

  • Milestone cleared.

  [bulk edit]

• 

  Ryan Bigg October 9th, 2010 @ 09:47 PM

  • Tag cleared.

  Automatic cleanup of spam.

• 

  Rohit Arondekar October 15th, 2010 @ 10:40 AM

  Any updates here?

• 

  José Valim October 15th, 2010 @ 10:47 AM

  • State changed from “open” to “stale”

  Please drop a comment if the leak still exists.

• 

  Jeremy Kemper October 15th, 2010 @ 11:01 PM

  • Milestone set to “3.0.2”

  [bulk edit]

• You flagged this item as spam.
  

  Anthony Burns November 5th, 2010 @ 05:56 PM

  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.